Engineers wiring transcript delivery into their own product or automation.
Developer integration guide for transcript packs and paid delivery
Developers should integrate against the app-level service routes, use ops status to detect live rails, and treat ACP jobs as the current public paid path.
Key facts
- Use the app routes under /api/service/*, not private backend-only paths.
- Check /api/service/ops/status before claiming a rail is live.
- ACP jobs are the current public paid integration surface for live settlement.
Start with the status surface
The service publishes an operational status route so developers can inspect publication state, acceptance scope, endpoint families, and rail truth before making buyer-facing claims.
That status route is the contract boundary between what exists in code and what should be considered public and production-usable.
- Read service publication state.
- Check acceptance scope before widening the public surface.
- Inspect rail-by-rail readiness before advertising a payment method.
Use the ACP jobs flow for live paid requests
For the live buyer path, the service exposes ACP offerings and ACP jobs. That flow is designed around the current Solana MPP settlement path and should be treated as the canonical public paid route.
- List offerings from /api/service/acp/offerings.
- Create paid jobs through /api/service/acp/jobs.
- Poll job state through /api/service/acp/jobs/{acpJobId}.
Handle delivery artifacts as exports
Once a purchase is complete, delivery should flow through manifests and export URLs rather than ad hoc scraping or hidden storage assumptions.
That keeps downstream automation stable and makes receipts, orders, and entitlements auditable.
- Order timeline and receipt lookup for reconciliation.
- Pack manifest for export discovery.
- Export files for actual transcript consumption.
FAQ
Should I build directly against the ingestion service?
No. The app-level /api/service/* routes are the public contract. They normalize truth and avoid depending on internal-only backend details.
Can I expose x402 or Tempo rails today?
Not as live production rails unless the service status explicitly marks them live. Planned rails should stay labeled as planned.
How do I know whether a channel should be quoted or bought immediately?
Use the purchase mode returned by the service. Instant-buy, quote-only, and manual-review each map to a different buyer experience and should not be collapsed into one CTA.
Next steps
Related guides
How to buy transcript packs from the channel knowledge service
A factual guide to instant-buy offers, quote-only scopes, manual review, checkout, and transcript pack delivery.
Current payment rail status: what is live now vs planned
A truthful summary of the service payment rails, including the current live path and the difference between supported code and public production readiness.
Whole-channel pricing, queueing, and manual review
What whole-channel requests mean, when queue pressure matters, and why large channels can move into manual review.