We set up a @circle agent wallet from @bleso_a's agent stack series, ran it on codex (GPT - 5.5), and tested the full flow.
One prompt from the share link alone: the agent read the price out of a 402, paid $0.25 USDC through Circle gateway, and unlocked the NibShare.
Then it went further. discovered content on its own, purchased from a Subblog it found, left an onchain reputation rating on @arc.
Pulled its receipt from the Nibgate public ledger at the end. Same table humans show up in.
Our thesis has always been absolute creator control. Even the revenue model on our hosted surfaces:
@nibgate never custodies creator funds and cannot move them. Payments land in a contract owned by nobody — the split is enforced by immutable bytecode on @arc, not by policy.
Solid walkthrough @jed_bgs
If you need to privately share something for a price and don't wanna spin up a whole site, this is it.
NibShare does it in under 2 min... encrypted at rest, whitelist only the wallets you trust, set an expiry, forget about it, earn passively on @arc.
Every economy lives or dies on allocation.
The agent economy can settle anything instantly now, but it still can't tell quality from noise, so capital drifts to whoever shouts loudest.
We're building the signal for paid content on @arc.
"I have no idea what a @circle payment Gateway is. Can't I just pay the creator directly?" — the thing we kept hearing from readers and creators.
So we added the direct x402 rail to @nibgate — live on our SDK, Subblogs, and Nibshare.
The server issues the 402 challenge, your wallet sends USDC straight to the creator on @arc, the transfer is verified on-chain, and the unlock proof is minted. Receipts land on the Nibgate Ledger, same as gateway payments.
Part of a bigger update shipping this weekend — stay tuned 👀
📄 Nibgate now supports Documents — the 6th content type.
You can now gate Sheets, PDFs, Word docs, and text files like every other Nibgate resource: your bytes stay on your site (or a hosted Subblog), encrypted at rest, and unlockers pay USDC via x402 on @arc.
https://t.co/JticuVe2B7
Your content stays on your site — that's the Nibgate rule.
But Subblogs bend it: your posts live on our hosted subblogs, not your domain.
So we introduced encryption at rest — hosting the bytes doesn't mean seeing them.
That's the encryption lifecycle on @nibgate:
• Phase 1 · Upload — every paid body and gallery image is AES-256-GCM encrypted server-side before it reaches object storage. No plaintext ever persisted; a bucket leak is ciphertext only.
• Phase 2 · Teaser — the cover image is the only thing stored in the clear, so the lock teaser still shows readers what they're paying for.
• Phase 3 · Read — plaintext is decrypted just-in-time, one asset at a time, only after a verified x402 payment proof (USDC on @arc). Keys stay server-side and never appear in a public response.
Storage holds ciphertext. Readers get plaintext. That's the deal.
Full flow with the encryption lifecycle: https://t.co/pSlhaklECz
Been building @nibgate for almost a month now.
The open protocol for content discovery and gating on @arc.
Woke up to see the official @arc account replied to our post. That's the validation that keeps us going. 🔥
If you're a creator, spin up a subblog and let's ship!
An agent just bought access to your video in one HTTP request.
That's the flow on @nibgate: agents discover content, pay with USDC on @arc, and rate it on-chain.
The content never leaves the creator's site.
• Discover (free) — the agent pulls /.well-known/llms.txt and hits the hub for content cards. Read-only and free.
• Pay (one x402 round trip) — the site answers 402 + PAYMENT-REQUIRED, the agent signs a gasless EIP-3009 authorization, retries with a PAYMENT-SIGNATURE header, and gets the content back with an unlock proof and a receipt. Writer gets USDC on @arc.
• Repute (on-chain) — the agent signs rateContent, the tx lands on the reputation contract.
Good content climbs. Spam sinks.
Full flow with every endpoint: https://t.co/FSrggTYSlX
Cloudflare just gave AI agents a wallet.
The "payment is the credential" era is real now — and it's exactly the rails @nibgate is built on.
Agents discover content on our index for free, unlock it with USDC via x402 on @arc, and rate it on-chain.
Cloudflare handles the rails,
The Economic OS gets its content economy.
Wallets are here. Make sure your content is what agents spend on → https://t.co/exBLWoasjj
creators on @arc — where's your Nibgate Subblog?
your own domain, USDC unlocks, on-chain reputation, money straight to your wallet.
the easiest corner of the Economic OS you'll ever own. write once, get paid forever.
A week ago, we shipped Nibgate Subblogs. We noticed that non-technical creators needed a plug-in solution to monetization.
A week in, the results have been kind of insane:
• 29 subblogs created,
• 20+ creators onboarded,
• 469 posts, 235 behind paywalls,
• 1,100+ views,
• 226 unlocks, 100+ USDC revenue.
People and agents genuinely paying, on-chain, verified, and the creator keeps everything.
We're pushing more SDK features for subblog creators as fast as we can ship them on @arc@thecanteenapp.
Find out more info on subblogs here: https://t.co/AcIG1WeMil
We’re dropping a new product soon for creators who don’t self-host their pages yet.
Follow and turn on notifications to join the private beta and get exclusive perks! 🔔
Up until today, using Nibgate meant running your own access route.
- SDK import.
- Circle Gateway server.
- Env vars.
- A whole backend endpoint.
It worked...
But it was too much for most creators.
We just fixed that...
Built for @arc creators on @thecanteenapp