Buy Tickets With an AI Agent: TixBit CLI (Search → Listings → Link)

TixBit is a secondary resale ticket marketplace and is not the primary box office. Prices may be higher than face value.

The published tixbit CLI lets an agent search events, inspect listings, and prepare a Stripe Link purchase within a buyer's total USD limit. The buyer approves the spend in Link before the agent completes that same order. No TixBit developer API key is needed.

Use Node.js 22.12 or later and [email protected] or later. The published CLI skill has the full command and safety rules. Setting it up does not authorize a purchase.

Find a listing

npx tixbit@latest --version
npx tixbit search "lions at bills" --json
npx tixbit listings "$EVENT_ID" --page 1 --size 100 --json
npx tixbit seatmap "$EVENT_ID" --json

Read the event date and venue. Use the exact case-sensitive IDs returned by the CLI. Search prices are discovery data, and listings can change. Check the section, row, quantity options, and shown price before asking the buyer to choose a ticket. link start checks the current total against the buyer's limit.

For 4 to 12 character alphanumeric listing IDs, the older buy command can show a quote without paying:

npx tixbit buy "$LISTING_ID" --quantity 1 \
  --email [email protected] --max-price 250 --json

--max-price is the cap for the whole ticket order, not a bid or offer. TixBit has no buyer fees. Wallet network fees, when applicable, can be separate.

Buy with Stripe Link

Get approval for the exact event, listing, quantity, buyer email, and total limit. The buyer signs in to Link on the machine running the CLI:

npx @stripe/link-cli auth login
npx tixbit link start "$LISTING_ID" --quantity 1 \
  --email [email protected] --max-price 250

link start checks the server's current total and returns an approvalUrl and orderReference. It does not charge the buyer. Create this request only when the buyer is ready, send the URL at once, and wait for approval. The URL can expire.

After approval, complete the same order:

npx tixbit link complete "$ORDER_REFERENCE"

The CLI handles the one-time Link payment credential. Never paste a card number, payment token, or browser session into a prompt or command. A fulfilled result includes the order details and may include a receipt URL. Check ticket access through that URL and the buyer's delivery email.

If the result is pending or manual_review_required, repeat link complete with the same order reference to check the existing attempt. Do not start another checkout or send another payment. TixBit can reconcile a ticket purchase that Automatiq completes later. If the order stays pending, give support the order reference.

Other paths

tixbit checkout "$LISTING_ID" --quantity 1 --json returns a browser checkout URL. The buyer reviews and pays on the website. A CLI price cap does not transfer to that page.

tixbit purchase uses the Tempo MPP wallet rail and needs a funded wallet, an explicit total cap, --confirm, and a stable UUID v4 idempotency key. An unpaid 402 challenge check confirms the offered payment methods but does not prove a paid Tempo order works.

The older buy --confirm route needs a payment token from an authorized integration. It does not create a Link spend request. Use link start and link complete for a normal Link CLI purchase. The older buy route accepts 4 to 12 character alphanumeric listing IDs; the Link MPP route uses listing IDs supported by the server.

tixbit auth provides browser sign-in and wallet links. It does not log the CLI into a seller account. Seller API calls need an authorized seller integration. There is no offer, bid, negotiation, or unattended ticket hunt command.

For new tool connections, use TixBit MCP. Existing CLI users can read the published CLI skill and SDK command reference. For a buyer issue, use support.