Integrations
Stripe, read only. API, CLI and MCP.
Parka connects to Stripe to read payment events and exposes your partner program on the HTTP API, the CLI and the MCP server. No other vendors sit in the path.
Stripe
Stripe, read only
Parka makes one call to Stripe, a read of the event list. The Stripe client refuses every HTTP method except GET and refuses any other endpoint before the network is reached. Attribution rides the Stripe Checkout session onto the subscription, and the ledger records each commission from the collected event.
- Call
- GET /v1/events on api.stripe.com
- Key
- STRIPE_RESTRICTED_KEY with read access to events
- Reads
- Collected payments, refunds, disputes and subscription renewals
- Writes
- None. Every Stripe write call is refused with STRIPE_WRITE_REFUSED.
- Custody
- Parka never charges a card, holds funds or sends a payout. You pay partners on your own rails and a person records the receipt.
Surfaces
API, CLI and MCP
Every capability declares the API, the CLI and MCP. All three surfaces share the same capability ids, the same workspace isolation and the same refusal codes.
API
POST /v1/invoke
Workspace bearer key
One authenticated HTTP endpoint runs every capability. Send the capability id, the program scope and the JSON payload. The bearer key sets the workspace and refuses cross-workspace calls.
CLI
node src/ticket16/cli.mjs
TRUMPET_API_KEY and operator env
Run any capability from a terminal and get one JSON line on stdout. Operator commands sit beside it for workspace creation, migrations, held events and human approvals.
MCP
POST /mcp
Same listener and bearer key
Parka implements JSON-RPC 2.0 with tools/list and tools/call on the same listener as the API. When an agent calls a human gate, Parka freezes the input and creates an approval request.