Scribe Finance

Payments and subscriptions for AI agents. Set spending limits, subscribe to any service, pay per request. On-chain, transparent, developer ready.

[Scribe Finance @scribefinance]

Scribe Finance is the billing layer for the agentic economy: on-chain payments, subscriptions, and allowances that let AI agents pay for services autonomously, settled and now live on Robinhood Chain.

CA: 0xf054f28446042d85af287371be2e0eceee98179a

[Scribe Finance @scribefinance]

A reminder on what $SCRIBE actually does, since it is being talked about!

It is not the payment asset. Payments settle in USDG.

The token secures the Settlement Node network through staking, bonds the Plan Registry against spam, and governs protocol parameters.

Check it out 👇

[Scribe Finance @scribefinance]

$SCRIBE: what our token actually does

Scribe Finance settles payments in USDG. That does not change, and no token sits between an agent and the API it is trying to call. Forcing a volatile asset into a payment path is how you make a payment rail worse, not better. Agents need predictable unit costs, and stablecoins provide that.

$SCRIBE exists for the layer above settlement: the coordination and security of the network that makes those settlements trustworthy.

1. Facilitator staking and slashing

Facilitators are the operators that verify payment authorizations and trigger on-chain settlement on behalf of resource servers. During beta this role is run by Scribe Finance, which is a centralization we have disclosed plainly rather than buried. The endpoint is a permissionless network where anyone can run a facilitator.

That transition only works with economic security. An open facilitator set means operators who can equivocate, censor requests, or report settlements that did not occur. Reputation alone does not deter this, because a facilitator can be spun up for the cost of a server.

Facilitators post a $SCRIBE stake proportional to the settlement volume they are authorized to handle. Provably faulty behavior, verifiable against on-chain state, is slashable. The stake is not a yield product. It is collateral, and it exists so that the cost of misbehaving exceeds what can be extracted by misbehaving. Service providers choosing a facilitator can read its stake directly on-chain and price the counterparty risk themselves.

2. Plan Registry bonding

The Plan Registry is the on-chain catalog where service providers publish pricing. Its usefulness depends entirely on its signal-to-noise ratio. An unbonded registry accumulates spam listings, impersonation of legitimate providers, and dead plans, at which point agents stop reading it and the discovery layer is worthless.

Publishing a plan requires a refundable $SCRIBE bond, returned when the plan is deprecated by its owner. For a provider running a real service, this is a rounding error against revenue. For anyone spraying thousands of junk listings, the capital requirement scales linearly and the bonds are recoverable only by cleaning up. The registry stays a catalog rather than a dumping ground, and it does so without a gatekeeper deciding who is allowed to list.

3. Protocol governance

There are live parameters in this system that materially affect people handling other people's money. Protocol fee rates. Slashing conditions and severity. Which stablecoins are supported for settlement. Facilitator admission criteria and minimum stake. Registry bond size.

Today those are set by us. That is appropriate for a beta and inappropriate for infrastructure that other businesses depend on. $SCRIBE holders govern those parameters on-chain, with proposals and outcomes publicly readable, so that the rules of the network are not a private decision made by a company that can be acquired, pivoted, or pressured.

Settlement in USDG. Coordination in $SCRIBE. That separation is deliberate.

[Scribe Finance @scribefinance]

@PaulAnthonyArr1 Always.

[Scribe Finance @scribefinance]

Two open standards define machine payments over HTTP. x402, stewarded by the Linux Foundation. MPP, from Stripe and Tempo, tracked at the IETF.

Scribe Finance speaks both.

One payment gate, either client, settled on Robinhood Chain. Your agent does not need to care which.

[Scribe Finance @scribefinance]

@cryptoo_alice Thank you so much for the trust and support! This only spurs us on to work harder for $SCRIBE!

[Scribe Finance @scribefinance]

@cryptoo_alice Always shipping. 💪

[Scribe Finance @scribefinance]

Addressing the coordinated FUD in public, once.

Someone has been demanding money from me, with the stated threat that they will keep publishing accusations that Scribe Finance is a scam and that our site drains wallets if I do not pay.

I am not paying. Here is the substance instead, so you can check it yourself rather than take my word or theirs.

On the wallet drainer claim

The site uses Privy for wallet connection. Privy is SOC 2 Type II certified non-custodial wallet infrastructure, acquired by Stripe in June 2025, and used in production by a large number of consumer crypto apps. Their own documentation states that embedded wallets are strictly non-custodial for both the application and for Privy itself. Key material is handled inside an isolated environment on a separate domain, which browser storage partitioning keeps out of reach of the host application's code.

What that means concretely: Scribe Finance has no authority over your wallet. We cannot move your funds. Every transaction requires your signature, and you see what you are signing before you sign it.

That last part is the check that matters most, and it does not require trusting me. Read the transaction in your wallet before approving. A drainer works by getting you to approve something you did not intend, usually an unlimited token approval to an address you did not choose. If you ever see that on our site, do not sign it, and post the transaction publicly.

On the source code

Everything is public. The smart contracts, the SDK, the site, the documentation.

https://t.co/isCqAyQMZm

The contracts are deployed and readable on the explorer. Every function that can move tokens is there to read. If anyone believes there is malicious code, they can point at the line. That is a lower bar than making the accusation, and nobody has cleared it.

I would rather someone audit this and find a real bug than have anyone take my word that there is none. If you find something, open an issue.

On the personal accusations

Lastly, someone found another person who actually looks a lot like me and started claiming that I am not who I am in my profile picture on GitHub. This feels like an extremely personal attack but I am looking past it. My webcam will be turned on throughout the whole AMA session that will be hosted in a few days, so obviously you guys can see I am who I am, with no lies.

Where this leaves things

Extortion works when the target is more afraid of the accusation than of paying. I am telling you about it because that is what removes the leverage.

Scrutinise the project. Ask me anything at the AMA. But scrutinise it on the code, which is public, rather than on claims from an account that told me privately it would stop making them for money.

[Scribe Finance @scribefinance]

We will be hosting an AMA on X Spaces, Sunday 31 August, 2:00pm UTC.

We will be doing a live walkthrough of the web app, and the TypeScript SDK for the developers.

Then answering open questions for as long as people keep asking them.

Set a reminder!

[Scribe Finance @scribefinance]

@Cryptoo_Gems Building even harder now. $SCRIBE

[Scribe Finance @scribefinance]

@rolexthexplorer See you there!

[Scribe Finance @scribefinance]

We will be hosting an AMA on X Spaces, Sunday 31 August, 2:00pm UTC.

We will be doing a live walkthrough of the web app, and the TypeScript SDK for the developers.

Then answering open questions for as long as people keep asking them.

Set a reminder!

[Scribe Finance @scribefinance]

@crypto_ideology That's the plan! Going to ship even harder now. This is just fuel to work even harder for $SCRIBE.

[Scribe Finance @scribefinance]

@zhukaiwei2 That's the plan! Shipping even harder now.

[Scribe Finance @scribefinance]

@crypto_ideology See you there!

[Scribe Finance @scribefinance]

@cryptoo_alice Thank you so much for the support!

[Scribe Finance @scribefinance]

@Cryptoo_Gems @cryptoo_alice Thank you for the support!

[Scribe Finance @scribefinance]

@martin_m1e 💪

[Scribe Finance @scribefinance]

@crypto_ideology 💪

[Scribe Finance @scribefinance]

Thank you all for 200 followers. 🥳

We will schedule an AMA on X Spaces in the next 2 days!

More details to come.

[Scribe Finance @scribefinance]

getAllowances lands: read many allowances in one call.

Same shape as the batch read added to Subscriptions. Unknown ids revert rather than returning a zeroed struct, so a dashboard cannot silently render an allowance that does not exist.

View commit here: https://t.co/MGOM38yQVO

[Scribe Finance @scribefinance]

The official Scribe Finance Telegram Community is now open!

Join here: https://t.co/e8IuwD7x2Q

Product questions, integration help, and build updates as they land.

Also, we will never DM you first, never ask for keys, and never send you a contract address. Stay safe.