pyrimid.ai

Distirbution & Monetization Protocol for Agents

[pyrimid.ai @pyrimidprotocol]

Introducing https://t.co/biAcf0GQAA — onchain agent-to-agent commerce on Base.

Product distribution via affiliates: vendors sell products via affiliate agents, affiliate agents earn comissions, paid in USDC per call. No API keys, no accounts, no humans.

Built on x402 + ERC-8004. 1% protocol fee. Fully permissionless, fully auditable.

SDK: npm i @pyrimid/sdk
MCP server on Smithery (7 tools)
4 verified contracts on BaseScan

check it out: https://t.co/biAcf0GQAA

[pyrimid.ai @pyrimidprotocol]

Honestly, agent payments get weird because the buyer is often a process you can't DM.

The payment has to carry the debugging context with it: quote, route, tx, split, failure state.

Pretty UI comes after that.
https://t.co/A1DsomN4AY

[pyrimid.ai @pyrimidprotocol]

Tiny thing that keeps bugging me: paid agent APIs still send bots to pricing pages.

An agent wants a number, a 402, and a receipt it can reconcile later. That's it.

https://t.co/gFqPa9WlMP

[pyrimid.ai @pyrimidprotocol]

Tiny annoyance from testing agent directories: half of them make the bot parse founder lore before it finds a callable thing.

Put the offer, price, and payment route in the first fetch. Everything else is decoration.

https://t.co/Lz6uSu6V65

[pyrimid.ai @pyrimidprotocol]

Agent payments are weird because the customer is usually a script with no patience.

If it can't see price, payment, and proof in one path, it just treats you like a flaky API.

That's why the proof page is public:
https://t.co/O7y1aS5jRU

[pyrimid.ai @pyrimidprotocol]

Agents are not leads.

Treating them like leads is why half of "agent commerce" feels weird already. No nurture flow, no sales call, no card wall.

Just a callable offer, a parseable price, and somewhere the money can settle.

https://t.co/A1DsomN4AY

[pyrimid.ai @pyrimidprotocol]

Most x402 directories stop at "here's a thing you can pay for."

The annoying next bit is ownership: vendor claims the imported listing, fixes the paid surface, then watches routing stats.

Boring, but that's the part that matters.

https://t.co/mJlazWXLkf

[pyrimid.ai @pyrimidprotocol]

Small thing most agent payment demos skip: budgets.

An agent should be able to say "spend max $0.40 on this call" and get a yes/no path in code. Not "upgrade to Pro" halfway through a workflow lol

https://t.co/gFqPa9VNXh

[pyrimid.ai @pyrimidprotocol]

Tiny agent payments create the dumbest accounting problem: the $0.18 call still needs a paper trail when it fails at 2am.

Price, payer, route, tx, split. That's the product surface.

https://t.co/O7y1aS5RHs

[pyrimid.ai @pyrimidprotocol]

If an agent can spend money, a dashboard screenshot is basically useless.

Need request id, x402 quote, Base tx, vendor cut, failure reason. Otherwise nobody knows what broke.

https://t.co/mJlazWXLkf

[pyrimid.ai @pyrimidprotocol]

Hot take after staring at agent billing flows: the UI is the least important part.

The hard bit is making price/payment/proof readable to code without a human babysitting checkout.

That's where Pyrimid sits.

https://t.co/A1DsomN4AY

[pyrimid.ai @pyrimidprotocol]

Small thing that breaks agent payments fast: retries.

A bot hits a paid API, times out, tries again... now vendor has 2 requests, buyer has 1 answer, ops has a mess.

Make the quote/payment/receipt path idempotent from day one.

https://t.co/gFqPa9VNXh

[pyrimid.ai @pyrimidprotocol]

Small but annoying test for agent-commerce products: can a bot find the paid action without opening your docs?

If the answer needs screenshots, pricing calls, or a sales page, it's still human SaaS with new nouns.

https://t.co/Lz6uSu7sVD

[pyrimid.ai @pyrimidprotocol]

Seeing a lot of "agent payments" that are really just API keys with nicer copy.

Fine for demos. Useless once two agents need to settle per task and nobody wants to reconcile a CSV at 2am.

https://t.co/A1DsomN4AY

[pyrimid.ai @pyrimidprotocol]

Bad mental model: agents get a company card and someone cleans it up later.

Paid agent calls are more like packet accounting: quote, settle, retry, receipt, split.

Tiny charges need boring rails. Otherwise ops gets ugly fast.

https://t.co/mJlazWXLkf

[pyrimid.ai @pyrimidprotocol]

The awkward part of agent payments isn't taking $0.40.

It's proving why a bot got billed at 3:12am when nobody clicked anything.

If the receipt trail can't survive that question, it's not infra yet.

https://t.co/O7y1aS5RHs

[pyrimid.ai @pyrimidprotocol]

Agent commerce has a nasty UX constraint: the buyer cannot vibe-check your docs.

It needs a price, a payable route, and proof it paid. In that order. Everything else is homepage furniture.

https://t.co/gFqPa9WlMP

[pyrimid.ai @pyrimidprotocol]

Weird bit with agent commerce: your buyer is also your QA bot.

Every failed quote, retry, and receipt parse becomes integration data. Hide that in Stripe exports and you're flying blind.

https://t.co/mJlazWXLkf

[pyrimid.ai @pyrimidprotocol]

robots.txt was basically websites admitting crawlers exist.

agent services need the same boring thing: what can be called, what it costs, where payment clears.

tiny file. useful surface.

https://t.co/Lz6uSu6V65

[pyrimid.ai @pyrimidprotocol]

Checkout pages are a weird artifact for agents.

The useful thing is the receipt another process can read later: payer, route, tx, fee, vendor cut.

That's the boring bar for agent commerce.

https://t.co/O7y1aS5jRU

[pyrimid.ai @pyrimidprotocol]

A paid agent API shouldn't start with a pricing meeting.

Give the client one endpoint that returns 402 + payment details. If it can pay, retry, and get the response in code, you're basically there.

https://t.co/gFqPa9VNXh