Give agents scoped access to an API. Revoke access without rotating anything else.
Approve an agent once with a passkey — no wallet required. It gets its own key and short-lived sessions scoped to exactly what you allowed. Remove one agent without touching the others. No shared API key to paste, leak or rotate.
Want a throwaway try first? Use the demo. It is not an account. Yours / a BRC-100 wallet stays optional for the BSV community.
How it works
-
The agent asks to connect
On the agent’s machine, run
txpass-agent connect imprintai-api. It creates its own key locally and prints a link and a short code. -
You approve with one signature
Open the link, check the code matches, choose what the agent may do and for how long, and approve with one passkey (or optional wallet) signature.
-
The agent works on short sessions
The agent mints 15–60 minute sessions with its own key. Txpass signs those session tokens — we never see your identity key. The API verifies them locally. Remove the agent, or revoke the whole policy, whenever you like.
Sessions
Sessions are only half of it. Agent sessions stay short (15–60 minutes) and are minted from the entitlement. Sessions are tokens Txpass signs and the API checks locally.
Entitlement receipt
Paid access rests on a subscription receipt: one BSV transaction with a txpass / v1 / sub OP_RETURN. That receipt is the entitlement signal — product, plan, validity window, and your identity I (as an identity commitment). It is a record, not a payment: the publisher bills you the way it already does, then asks Txpass to record the subscription, and Txpass builds, funds and publishes the receipt. There are no prices on the receipt. Renewals chain on from the current receipt, and cancellations or refunds revoke it. Entitlements are receipts on chain. Receipt fields in Protocol v1 →
What the API checks
When the API accepts a session, it verifies the JWT locally (true or false). Both are true: sessions are tokens Txpass signs and the API checks locally; entitlements are receipts on chain.
What the agent sees
One command, one approval. The agent never receives a long-lived secret: it holds a key that only works for what you approved, and the sessions it mints expire on their own.
- No API key in
.envfiles, prompts or chat logs - Each agent has its own key, scope and daily cap
- You see which agents are connected and remove any one of them
- We never see your identity key; Txpass signs the session tokens
- APIs check sessions locally, without calling Txpass on every request
Who it’s for
API publishers
Integrate Txpass on your API so agents can use it beside your existing API keys. Verify short-lived JWTs against a public key set. Bill your users however you already do.
Calls made with a Txpass session count toward the user's existing usage limits once you link their Txpass identity to their account in your system. Txpass doesn't meter calls or create a separate quota; linking and enforcing limits stay with you.
Verification is free. Txpass does not charge publishers a per-call fee, a listing fee, or a platform cut. You bill your users however you already do. If we ever sell publisher-side extras (support, SLA, a directory), verification stays free.
People running agents
Give coding agents, research bots and automations access to paid APIs on your plan, without handing over a key you can’t take back. Agents can only use Txpass with API publishers that have integrated it — today that is Imprint.
Teams
One policy, many agents, each with its own key. When someone leaves or a machine is lost, remove that agent. Nothing else breaks. Teams can only use Txpass with API publishers that have integrated it — today that is Imprint.
Live today
- The account page: sign in with a passkey (Yours / BRC-100 wallet optional), see your plans, manage agent policies and one-off delegations
- Agent-initiated connect:
txpass-agent connect, one passkey (or wallet) signature to approve - Publisher verification with short-lived JWTs and a public JWKS
- First publisher: the ImprintAI Provenance API
Txpass is in early access and free to use. See pricing for what we expect to charge for later.