Article / rich post

Read · detail. One H1, a readable measure, then evidence. The original is a citation, not a skin.

Open original (Vercel, 25 Aug 2026)

Original (cited)

Live URL: vercel.com/blog/the-end-of-credential-sprawl-for-agents

Our crop is a block map of reading order (2026-08-30). No Vercel assets in CSS.

product chrome (out of scope)
H1  The end of credential sprawl for agents
    authors · date · 6 min read
lead + in-body product link (Vercel Connect)
hero product image (light/dark pair)
H2  Vaults don't fix long-lived tokens
    prose · CLI snippet · code sample
H2  What changes when access becomes a request
    comparison table
H2  Connectors for the services you already use
H2  Pricing and availability
related / explore cards
Ready to deploy?  (marketing CTA)
site footer

Gelium remake

This is how that structure lands in Gelium: same jobs (title, byline, lead, H2 evidence, table, related), our copy, tokens, no their brand. It is not /recipes/rich-article (a different media fixture).

Read · article fixture

Access as a request

By Gelium UI · 30 Aug 2026 · 6 min read

Long-lived secrets turn every agent into a standing grant. Issue access at the moment of the task, scoped to that task, and let it expire.

No hero pair. A Read page does not need a light/dark marketing image to start. Evidence belongs in the body.

Standing tokens do not expire with the job

A vault hides a secret. It does not limit what the secret can do after it leaks. Rotation scripts and copied environment values are a second workload.

gelium access mint slack --name ops-bot
# identity comes from the runtime, not a second env secret

What changes when access is requested

Stored token versus request-time access
Property	Stored token	Request-time
Lifetime	Until someone rotates it	Short-lived, refreshed
Reach	Everything the agent might need	Scoped to this step
Revocation	Redeploy copies	One command

Connectors you already run

Availability

Say who can request access and which environments are allowed. Pricing copy belongs on a pricing screen, not as a second primary on the article.

Keep / adapt

Kept	Gelium primitive	Rejected	Why
One title + lead + byline	article header	Product mega-nav	Not this page’s chrome
Descriptive H2/H3 evidence	headings + prose + `pre`	Copy-link-to-heading chrome	Extra JS
Comparison table	`ui-data-table`	Light/dark decorative hero pair	Skin, not structure
Related content	`ui-list` + nav	“Ready to deploy?” band	Second primary on a Read page
Evidence in the body	note + table	External embed / tweet row	`MEDIA-EMBED`

Ask before copying

Related stories as a list, or omit?
Native media in the body, or prose + table only?
Article JSON-LD on the consumer host, not copied from Vercel?