Publisher guide

Publisher dashboard

The publisher dashboard at txpass.app/publisher is where API publishers manage how their product appears to users and agents. This first version is very basic and free during early access; it exists to collect feedback. Plans, paid configuration, policies, teams and a general browser-origin editor are not in it yet. One staging host per product is.

Sign in

Connect the wallet that holds your owner key (Yours 5.x or another BRC-100 wallet). There are no passwords and no cookies: every call the page makes is signed by your wallet, exactly like the account page.

What you can do

  1. See your products. Each product you own shows its name, description, status (Live or Waiting for Txpass review), its routes, and totals: active entitlements, agent policies, agents, one-off delegations and agent sessions today (UTC). These are counts only. Txpass never shows you who your users or their agents are.

  2. Write your route copy. You supply the wording; Txpass only checks the format. For each route: a label (what it does, 1–60 characters), a group (1–32 characters, for example "Imprints"), Read or Write, and whether it is recommended for agents (at least one route must be). Allowed characters are letters, digits, spaces and . , ' ( ) - / &; no links, no HTML. One save is one wallet signature. The public catalog (GET /v1/products), the scope pickers on /account and txpass-agent connect then use your copy. Labels are for display only: tokens always carry just METHOD /path. Routes without a label show as the raw METHOD /path, and routes without a group show under "Other".

  3. Add a product. Give a name, a product id (lowercase with dashes; it cannot change later because it is inside every token), an optional description, the API base URL (https), the routes that accept a Txpass session (METHOD /path, one per line) and a contact email. The request is private (only you and Txpass see it) and not live until Txpass approves it. After sending, label and group its routes and pick the recommended set; Txpass can approve it only then.

  4. Sign in with Txpass. List the origins of the sites that show a Continue with Txpass button for this product (one per line, https:// or http://localhost for testing, at most 10). One save is one wallet signature; an empty list turns the button off. See Sign in with Txpass.

Built-in products

Products that Txpass configured before the dashboard existed (today: imprintai-api) get their owners set by Txpass on request. The labels you see first are a stand-in written by Txpass; replace them with yours. Nothing about the product changes until your first save; after that, the catalog serves your copy.

Staging trial and the agent brief

On each product, set one staging host and tick the existing routes an agent should use there. Saving does not publish the product and does not turn free enrolment on. Free enrolment stays blocked unless you have already opted in.

Verification of a session token is free. You bill your users. Calls made with a Txpass session still count toward that user's existing limits.

Give your coding agent these two URLs (also copied from the product card):

  • GET /v1/products/<product id> — the product document (routes, policy, staging host)
  • GET /v1/adopt/<product id>/agent-brief.md — the same facts as a filled prompt

If you have not saved a staging host, the brief says so. It does not invent one. GET /.well-known/txpass.json only points at those two URL patterns.

Not in this version

Pay-to address or seller (these will need a wallet signature, a 24-hour delay and an email to all contacts); a mandatory second owner key (the page reminds you to add one); emails; analytics beyond totals; a general browser-origin list beyond the one staging host; adding or removing routes of a live product; and self-serve go-live.

API details: Facilitator API, publisher dashboard routes.