Publisher FAQ
FAQ
Does Txpass replace my API keys?
No. Txpass is an optional dual-rail beside your existing API-key auth. Keys stay for non-wallet buyers. You do not cut over to Txpass-only in v1.
Do I give Txpass my API keys?
No. You keep serving your API. Txpass never holds or proxies your publisher API keys. Buyers either present your key (as today) or a short-lived Txpass session JWT that your API verifies locally.
Can someone access my API without an API key if I enable Txpass?
Yes — that is the point of the wallet path. Call it the second ignition: a second authenticated way in, not a bypass of auth.
You control how open that path is:
on_new_identity=rejectvsauto_enroll- which plans map to which local tiers
- which routes accept Txpass
- CORS origins for browser AuthFetch
- quotas and plan allowlists
Enabling Txpass does not mean “anyone with a wallet gets in.” Policy does.
What's the safe production default?
on_new_identity=reject, with paid access via on-chain receipts. Free auto-enroll is an explicit opt-in (common for staging dogfood; not the production default unless you choose it and set quotas).
How do paid upgrades work?
The receipt is the subscription. A buyer pays on-chain; the facilitator (or any compliant verifier) ingests the txpass / v1 / sub subscribe tx and the entitlement becomes live. There is no publisher “grant premium” admin API as the source of truth.
A Stripe (or similar) bridge may come later as an optional path that still ends in a verifiable entitlement — not as a replacement for the receipt model.
What about free tier?
Free is facilitator-issued auto-enroll, not on-chain. Synthetic receipt_txid looks like autoenroll: + 32 hex. Plan-dependent rules apply: free expects that shape; paid expects a 64-hex on-chain txid. Do not mix them.
Do buyers give me their private keys?
Never. Buyers use BYOW (bring your own wallet) with AuthFetch / BRC-103. Your API never receives a private key or WIF.
Human vs agent onboarding — which is first-class?
Both. Coding agents are the preferred integrator (copy-paste brief or live discovery). Humans supply product decisions — slug, origins, issuer, secrets — when asked. Agent brief is optional but recommended; humans set secrets and policy.
What if Txpass shuts down?
Paid entitlements live in on-chain receipts. A third party can authorize the same receipt with the portable verifier (@txpass/verify + protocol docs) without calling txpass.app. The hosted index is a convenience cache, not the source of truth for paid access.
Is AuthFetch required on my API?
No (thin path). Buyers AuthFetch the facilitator to mint a session JWT. Your API verifies Authorization: Bearer <jwt> via JWKS (GET /v1/session/jwks) or @txpass/verify (verifySessionJwt). You do not have to run AuthFetch middleware on every product route.