What we are building
Saifuro authorizes agent payments in production today: one integration, every rail, a signed verdict on every spend. This is where the product goes next for the teams already running agents on it, quarter by quarter: the policy engine, the console, escrow, new rails and the developer platform. Quarters are targets, not commitments; when something moves, the page moves with it.
Q4 2026
Policies over the API and in the console, a log an auditor can recompute, and agents that get controls with one import.
Signed log checkpoints
Signed checkpoints of the decision log, so an auditor recomputes the chain from an export and checks it against our published key without asking us.
Policies over the API
Create, diff and roll back policy versions programmatically, with rules set per mandate and an explanation attached to every decision.
Policy editor
Draft, diff and publish policy versions in the console, with a change history a controller can read.
Review queues and enforcement history
List pending reviews over the API, read who approved what, and replay every enforcement change alongside the decisions it affected.
MCP server and framework integrations
Agents built on the OpenAI Agents SDK, LangChain and the Vercel AI SDK get spending controls with one import.
Webhook replay and delivery logs
Replay any event from the last thirty days and see every delivery attempt, so a missed webhook is a lookup rather than an incident.
Q1 2027
Self-serve access, public SDKs, team management, and a month close that runs itself.
Self-serve sandbox
Sign up, get sandbox keys and run the first authorization in minutes, without a call.
Public SDKs
The TypeScript SDK on npm for everyone and a Python SDK alongside it, both generated from the same OpenAPI description as the reference.
Signed verdict v2
Currency and audience under the signature, so a verdict states what it authorizes and who it was issued for. Introduced as a versioned change, announced ahead of time.
Team management
SCIM provisioning, granular roles per policy and per agent, and a per-user audit trail of every approval and policy change.
Finance close automation
Settlements matched to decisions automatically, postings by agent and vendor, and a month-close pack a controller posts in one step.
Milestone escrow
Deals with several deliverables and partial releases, each release against its own signed verdict.
Q2 2027
More chains, more bank rails, native accounting connectors, and policy changes you can rehearse.
Escrow and settlement on more chains
Ethereum, Arbitrum and Polygon alongside Base and Solana, with the same policy on every chain.
Bank rails in more regions
SEPA Instant, Faster Payments and PIX payouts through licensed providers, so one budget covers invoices in every region an agent buys from.
Accounting connectors
Native connectors for NetSuite, QuickBooks and Xero, mapped to your chart of accounts and reconciled line by line against the decision log.
Policy simulation
Replay a policy change against the last thirty days of decisions and see what it would have allowed, held or refused before it goes live.
Budget forecasting
Burn-rate projections per agent and vendor, with alerts ahead of a limit rather than at it.
Multi-party escrow
One deal, several sellers and split releases, for marketplaces where an agent buys from more than one counterparty at once.
H2 2027
New regions, agent identity, escrow beyond chain, and intelligence across the whole fleet.
US and APAC regions
Deployments in the United States and Asia-Pacific with residency terms in the contract, for customers whose auditors care where the log lives.
Verifiable agent identity
Mandates bound to attested agent identities, so a verdict says not only what was allowed but which agent, provably, asked.
Log streaming
Decisions delivered to your SIEM and data warehouse as they happen, with the same signed records as the export.
Spend intelligence
Forecasts across the agent fleet, benchmarks per category, and recommended limits derived from what agents actually did.
Escrow on card and bank rails
Escrow for deals that settle through licensed providers rather than on chain, with the same release and refund rules.
HOW THIS PAGE WORKS
An item is added when it is decided, moves when we learn something, and leaves this page when it is live and documented in the reference.
WHAT EXISTS TODAY
The API reference at docs.saifuro.com is the record of what is live now, and what we do not claim lists the boundaries we keep on purpose: no custody, no transaction signing, no screening.
TELL US WHAT MATTERS
If one of these items decides whether you integrate, say so at contact@saifuro.com. Knowing which one matters beats our own ordering.
We are hiring the people who will ship it
Ledger, protocol, smart contract and developer relations engineers. Interviews are run by the founders, and the work sample is paid.