2/
Also today: the curation timelock we queued 48h ago executed on chain.
Queue → wait → apply. No admin key that can skip the wait.
Slow on purpose. That's the point of a timelock.
The SDK is live on npm.
npm i @tabai/sdk
One line of config and your service bills agents post-paid. They get the response first. You get settled after, backed by a Bond.
No prepay. No withheld responses. No trust required.
2/
Applied → Confirmed.
Applied → Reversed.
Both exercised on chain, not just in tests.
If your credit system has never survived a default, you don't actually know that it works.
Most payment systems only test the happy path.
Yesterday we ran the one nobody tests: the agent didn't pay.
The clearing expired. The Bond covered it. The Service was made whole automatically, on chain.
Every branch of the state machine has now run for real.
Tab is open source.
We're building the SDK and verification tooling around the protocol now.
If you're building AI agents that need to pay for APIs, compute, data, tools, or other services:
What would you want them to be able to buy on credit?
Reply, We’re genuinely curious.
AI agents are expected to pay before they get access.
We built the opposite.
Tab lets agents consume a service first, keep working, and settle later.
Post-paid billing + a credit facility, enforced onchain.
Tab is built on @Creditcoin, with settlement against Eth.
The system has been exercised beyond the happy path, including real failures that forced changes to the contracts.
We're building this as infrastructure for agents that need to buy, consume, and transact autonomously.