The Publisher Developer Portal for Payment-Enabled AI Tools

TL;DR

• The Publisher Developer Portal is where MCP server operators integrate with Shatale, validate their server in sandbox, ship to production, and monitor agent traffic.
• Five tabs do most of the work: Go-Live Checklist, Sandbox, API Reference, Webhook Inspector, Health Metrics.
• Most publishers go from signup to first sandbox transaction in under 30 minutes.

The Publisher Developer Portal is Shatale's dashboard for MCP server operators. It bundles the tools you need to launch a payment-enabled MCP server — sandbox, API docs, webhook debugging, and post-launch monitoring — into one interface.

What's in the portal?

Five tabs, each solving a specific problem in the integration journey:

1. Go-Live Checklist

A step-by-step list of everything that needs to be true before you can switch to production credentials. Items include: KYB completion, webhook endpoint verification, sandbox transaction success, terms acceptance, payout method connected. Each item links to where you complete it.

2. Sandbox

The full Shatale API surfaced in a sandbox environment. Issue test cards, run test transactions, simulate declines, fire test webhooks. No real funds; no rate limits worth worrying about.

3. API Reference

Live API docs with try-it-now request builder. Each endpoint shows: parameters, sample requests, sample responses, error codes, idempotency rules. Code samples in curl, Python, Node, Go.

4. Webhook Inspector

Real-time stream of webhook events delivered to your endpoint, with payload viewer, response status, retry history, and replay button. Filter by event type, time range, or specific request_id.

5. Health Metrics

Production-only. Shows your integration's health: success rate, latency p99, decline rate by reason code, top agents by volume, top merchants. Alert thresholds configurable per metric.

What's the typical first-week journey?

Day 1: Sign up, complete KYB basics, generate sandbox API key. Run the quickstart in the Sandbox tab to confirm the connection works.

Day 2-3: Implement the MCP server's payment_required flow. Use the Sandbox tab to run end-to-end test cases — successful charges, declined charges, refunds.

Day 4: Set up your webhook endpoint. Use the Webhook Inspector to confirm events fire correctly. Implement signature verification (sample code in API Reference).

Day 5-7: Run the Go-Live Checklist. Complete KYB fully, connect payout method, verify webhook signing, accept terms. Submit for production review.

Production access typically lands within 1-2 business days after submission.

What does post-launch look like?

The Health Metrics tab is what you'll live in. Key dashboards:

• Success rate — % of agent calls that complete successfully (paid + tool returns ok). Target ≥ 98%.
• Latency p99 — end-to-end including payment + tool execution. Target ≤ 500ms for sub-task calls.
• Decline rate by reason — what's breaking and why. Top reasons usually mean a policy mismatch, not a fraud signal.
• Top agents — which agent products are sending the most traffic. Useful for partnership conversations.
• Top tools — within your MCP server, which tools are being called. Useful for pricing decisions.

Alerts can be configured per metric. The default is decline rate > 5% sends an email.

What about debugging when things go wrong?

Three tools for incident response:

Webhook Inspector replay. A webhook delivery that failed because your endpoint was down? Replay it from the inspector once you're back up.

Trace lookup. Every charge has a request_id that lets you trace through Shatale → your server → back to the agent. Paste a request_id and see the full event chain.

Decline reason explainability. Every decline has a structured reason code AND a human-readable explanation that tells you exactly which rule fired.

Live chat with support is in the bottom-right of every page.

What if I'm not building an MCP server — just integrating with Shatale as an agent platform?

Most of the portal is still relevant:

• API Reference applies regardless of whether you're a publisher or an agent operator.
• Webhook Inspector applies for any account.
• Health Metrics shows agent-side stats (how often your agents got declined, by what merchants).

The Go-Live Checklist and Sandbox are tailored for publishers, but agent platforms can use them similarly.

FAQ

Is the portal free?

Yes. Sandbox is free. Production has per-transaction fees + a monthly platform minimum. See pricing at shatale.com/pricing.

Can multiple team members access the portal?

Yes. Invite teammates from Settings → Team. Roles: Owner, Admin, Developer (write API keys, no billing), Viewer (read-only).

How long does production review take?

Typically 1-2 business days after KYB completion. Expedited review available for partners with prior fintech experience.

What if my webhook endpoint goes down?

Shatale retries with exponential backoff for 24 hours. After 24 hours of failures, the endpoint is paused and you'll get an alert. Use the Webhook Inspector to replay events once you're back online.

Can I download my data?

Yes. Health Metrics, transaction history, and webhook delivery logs are all exportable as CSV. Programmatic export via API for compliance use.

Related reading

• [How to List Your MCP Server in Shatale's Catalog](/blog/list-mcp-server-shatale-catalog) — get discovered

External references

• [Model Context Protocol specification](https://modelcontextprotocol.io) — the protocol your MCP server speaks
• [MCP server registry](https://github.com/modelcontextprotocol/servers) — community-maintained list

---

By Ted L.. Last updated 2026-04-29.