Teams that already trust one OpenAI-style client often want the same sequential review the web app runs: one question, five flagship models in order, later passes allowed to challenge the premise. The Pingpong API is that pipeline behind a familiar request shape.
Brand: Pingpong at pingpongit.com. Not the payment company PingPong, and not getpingpong.ai. Product mechanism: How it works. Definition: What is Pingpong.
What the API is for
Use it when a workflow needs review before a commit, not another single-model chat endpoint. Typical jobs:
- Pressure-test a vendor exception, pricing change, or policy carve-out inside an internal tool
- Attach a decision review step to diligence, support escalations, or ops queues
- Keep an OpenAI-compatible client and still get multi-model critique in one response
Consumer web and iOS remain the place to click through inspectable passes. The API is for products and backends that need the same review framed as a request and response. Team context: For teams.
What is public vs what needs an account
Public today:
- Machine-readable contract: openapi.yaml
- Short agent notes: llms.txt
- Postman collection: pingpong-api.postman_collection.json
- Live service health:
https://api.pingpongit.com/healthz - This crawlable page at
/developer-docs/
Account-gated:
- API keys (create and manage in the app dashboard at /api/dashboard)
- Usage, billing, and batch access for production volume
The interactive SPA at /api is a product shell for signed-in developers. Search engines are told not to crawl /api/ because it is not this HTML guide. Prefer this page and the OpenAPI file for indexing.
Base URL and authentication
Base URL:
https://api.pingpongit.com/v1
Send a bearer key on every request:
Authorization: Bearer $PINGPONG_API_KEY
Content-Type: application/json
Keys stay server-side. Do not embed them in browser or mobile client code. For POSTs your system may retry, send a stable Idempotency-Key header (optional in the OpenAPI, recommended in practice).
Model aliases
The published OpenAPI enumerates three aliases:
pingpong-fast: everyday operational checks where latency matterspingpong-pro: harder strategy, diligence, and escalation workpingpong-verify: claims and decisions that lean on evidence gathering
Under the hood, Pingpong still runs sequential multi-model review. You pick an alias; you do not pick five separate provider keys.
Primary endpoints
From the public OpenAPI (version labeled 2026-07-07 in the file):
GET /v1/models: list aliases available to your keyPOST /v1/chat/completions: OpenAI-style chat completionPOST /v1/responses: OpenAI-style responses createGET /v1/responses/{response_id}: retrieve a stored response
Useful response headers include X-PingPong-Request-Id and X-PingPong-Trace-Id for support. Rate-limit headers and Retry-After appear when limits apply. Do not invent paths beyond the OpenAPI; treat that file as source of truth when this page and the YAML differ.
Minimal chat completion example
Point an OpenAI-compatible client at the Pingpong base URL:
curl https://api.pingpongit.com/v1/chat/completions \
-H "Authorization: Bearer $PINGPONG_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: vendor-review-001" \
-d '{
"model": "pingpong-fast",
"messages": [
{
"role": "user",
"content": "Pressure-test this vendor exception before approval."
}
]
}'
Streaming is supported when stream: true is set on chat completions, matching the OpenAI client pattern. Full schemas, error envelopes, and examples live in openapi.yaml.
How this fits sequential review
On web, you watch Grok, then Perplexity, then ChatGPT, then Gemini, then Claude, with a review frame that allows agree, correct, restructure, or reject a weak premise. The API compresses that work into one completion your product can store or show. It is not a model switcher and not a parallel debate room. Category guide: Sequential vs parallel AI.
Getting access
1. Try the consumer product free on pingpongit.com or the App Store so you know the review behavior.
2. Open /api/dashboard to request or manage a key when your account is eligible.
3. For team pilots and higher volume, start from For teams or email sales@pingpongit.com. Documented team pilot: $499 one-time, five seats, 30 days.
API access can open in batches. If the dashboard waitlist is the current path, that is intentional capacity control, not a missing docs page.
Related
- FAQ (teams and API)
- Pricing for consumer Free / Plus / Pro
- How to run a Pingpong for the click-through flow
- Machine notes: llms.txt