Available prepaid API · deterministic JSON checks
Catch OpenAPI inconsistencies before an integration ships.
Check an OpenAPI JSON specification for structural and selected coherence issues. Give integration reviewers an explicit report instead of treating a declared contract as proof of runtime behavior.
No account or card for the browser tool. The browser report is unsigned; paid API calls return an ES256-signed report after payment confirmation.
Where it fits in an automation
Run a check on a supplied specification in your integration or release workflow. Review path parameters, local references, operation identifiers and declared security. The paid API can also compare two caller-supplied offers in the same currency and supplied observations; it never fetches their source independently.
OpenAPI 3.0.x uses its OpenAPI structure schema; OpenAPI 3.1.x receives selected coherence checks only, not full JSON Schema 2020-12 validation. External references are not fetched; referenced path items are not expanded. No legal-contract analysis, live endpoint testing, security audit or certification. Maximum 64 KiB input and 500 paths.
A fictitious example you can inspect
The input below is a complete synthetic paid-API request. For the free browser tool, paste only the document object; the paid API uses the whole envelope. The output shows selected analysis fields calculated by the actual free browser core; it is not a signed receipt, a customer result or evidence of a paid transaction.
Show the complete synthetic JSON input
{
"request_id": "synthetic-contract-001",
"document": {
"openapi": "3.0.3",
"info": {
"title": "Synthetic example",
"version": "1.0.0"
},
"paths": {
"/example": {
"get": {
"responses": {
"200": {
"description": "Successful synthetic response"
}
}
}
}
}
}
}Download this complete JSON example · Open the free tool
Calculated analysis output
{
"openapi": "3.0.3",
"structure_validation": "OpenAPI_3.0_schema",
"endpoint_count": 1,
"blocking_count": 0,
"warning_count": 2,
"findings": [
{
"code": "OPERATION_ID_MISSING",
"severity": "warning",
"path": "/paths/~1example/get",
"message": "Add a stable operationId for SDK and integration mapping."
},
{
"code": "PUBLIC_OPERATION",
"severity": "warning",
"path": "/paths/~1example/get",
"message": "This operation permits unauthenticated access in the contract; confirm that it is intentional."
}
]
}Read the findings, not only an HTTP status. A warning or discrepancy is an analysis result, not a failed transport request.
Price and purchase
EUR 0.010 excluding tax per check. Choose your exact total payment from EUR 10 to EUR 10,000, including applicable taxes. The net amount becomes a shared tax-exclusive balance for the three available services.
One-time payment, no subscription, no automatic recharge. Save your private recovery code before confirming payment; API access starts only after server confirmation. Different API capacities are alternative uses of one balance and cannot be added together.
A valid analysis with findings is charged; invalid input consumes no credit. Save each returned report and signature yourself. The prepaid service does not archive reports.
Choose my API budgetConnect after purchase
Your saved private code is already your Bearer API access. Keep it in protected server configuration, never in a frontend, prompt or URL. Read GET /v1/status without a debit and proceed only when state is active.
POST https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg/v1/contracts/check Authorization: Bearer YOUR_PRIVATE_BUDGET_CODE Content-Type: application/json Body: the complete JSON example above, reviewed before execution.
Use a new request_id for a new check. After an uncertain response, deliberately retry the identical body and identifier, not a fresh request. Limited reconstruction metadata lasts 30 days; it does not replace your report backup or expire the commercial balance.
Remote MCP uses protected custom Bearer headers, not OAuth. No universal client compatibility, automatic purchase or supplier payment is promised.