Use the published API contract for multi-model review. Use the separate PDF endpoint to format a narrative and evidence list you have already prepared.
Review API contract
The OpenAPI document describes the base URL https://api.pingpongit.com/v1, bearer authentication and these paths:
GET /v1/modelsPOST /v1/chat/completionsPOST /v1/responsesGET /v1/responses/{response_id}
The documented aliases are pingpong-fast, pingpong-pro and pingpong-verify. Confirm current access for your key before relying on an endpoint or model in production.
Account access
Use the API dashboard to view the access and key options available to your account. Keep keys server-side. A public schema or health response does not establish that a particular account has paid access.
PDF formatter
The PDF API uses POST https://pingpongit.com/api/dispute-evidence-pdf. It accepts a different payload and returns a file containing supplied text. It does not run the review pipeline or submit evidence to a processor.
Build a reliable integration
- Read the current schema and error responses.
- Check account eligibility and quota before production use.
- Validate the status and content type of every response.
- Handle retries according to the specific endpoint’s contract.
- Record human approval before any consequential external action.
Other references
Use the Postman collection and short agent reference. The agent workflow guide explains where review and formatting fit.