Roadmap

Tollstile is in early access. The core payment lifecycle is implemented, but some rails and runtime integrations still need production verification. The v0.1 release includes the implemented areas below.

v0.1

Still to verify

• The remaining rails against their live providers: Tempo Moderato for MPP, LND on regtest for L402, the Skyfire sandbox for KYAPay.
• x402's upto scheme, and any facilitator other than x402.org on a testnet.
• Run the Next.js and fetch adapters inside Next.js and on Workers, Deno, and Bun, and the D1 and Neon ledger adapters against those services.

After v0.1

• escrow flow (settle a deposit, then the final amount)
• OpenTelemetry package built on onEvent

Experiments

Things being tried in the open. Not API, not a standard, and not covered by any compatibility promise — they live in examples until something outside this project uses them.

A published price list

An agent that must contract with a provider before it can call anything is not buying software at the moment it needs it. Paying needs a rail; knowing the price needs nothing at all, and there was no machine-readable way to ask.

The demo serves one at /.well-known/tollstile:

{
  "call": "POST /v1/summarize",
  "price": "up to $0.50, then $0.001 per word",
  "plan": {
    "pricing": "up_to",
    "commitment": "request",
    "access": ["credits", "payPerCall"],
    "rails": [{ "rail": "test", "flow": "authorization", "settles": "after_handler", "onHandlerFailure": "release" }]
  }
}

plan is not a description someone maintains beside the code: it is the route's ExecutionPlan, the same object the gate enforces, so a published price cannot drift from the charged one. The example agent reads it before spending anything.

What would move this out of Experiments: something other than this demo reading one. If that happens, most of it is already in core — ExecutionPlan carries all of plan — and the rest is a route that serves it.

Out of scope