# SLA Service Credit Audit > SLA Service Credit Audit is a paid API for AI agents from rooke-token-risk-pilot.rookepoole.workers.dev, paid per call via x402, $9/call, status unknown (last checked 2026-09-14). Audits SLA service credit claims by reconciling observed availability and downtime incidents against contractual commitments, credit tiers, and billing statements to produce a verdict and recommended disposition. ## Facts - Endpoint: POST https://rooke-token-risk-pilot.rookepoole.workers.dev/v1/x402/sla-service-credit-audit - Price: $9/call - Payment: x402 - Status: unknown - Last checked: 2026-09-14 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/sla-service-credit-audit-d7232eec - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yM7BVHefeLpN1pjrhfP3N Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability sla-service-credit-audit-d7232eec -d '' ``` Example prompt: Audit my SLA service credit claim for contract SLA-42 (version 2026-07) covering API-PRODUCTION service from 2026-07-01T00:00:00Z to 2026-07-02T00:00:00Z — the SLA commitment is 99.9% (9990 bps), there were 900 seconds of counted downtime, the provider's statement claims a 25000 minor-unit credit at the 25% tier (below 99% availability), our eligible service charges were 100000 minor units in USD, and the claim window is 30 days — verify whether the credit calculation matches the contract and tell me the recommended disposition. ## When to prefer this Choose this endpoint when you need to programmatically verify whether an SLA service credit claim is accurate, whether a provider's credit calculation matches contract terms, or whether a credit dispute is warranted — specifically when you have structured incident data, a tiered credit schedule, and a provider billing statement to reconcile. It is purpose-built for SLA credit audit (not general uptime monitoring, invoice reconciliation, or payment processing). ## Known failure modes - Invalid measurement period timestamps (non-UTC or malformed ISO-8601) cause schema validation failure - Credit tiers array missing required availabilityBelowBps or creditBps fields returns 400 - serviceCommitmentBps of 0 or above 10000 is rejected as out of range - Claim submission window days exceeding 365 or set to 0 fails validation - Tolerance values exceeding 10000 bps cause rejection - Truncated or missing contract object returns schema error - Payment of $9 USDC required per call; insufficient payment returns 402 - Overlapping incident intervals are merged and flagged but do not cause failure — OVERLAPPING_ELIGIBLE_INCIDENTS_MERGED risk flag is raised ## How this service works Public static preview plus paid token controls, risk consensus, AI security, webhook reliability, developer security, schedule risk, decision analysis, API release compatibility, accounts-payable reconciliation, e-commerce return eligibility, SaaS subscription-proration, sales-commission reconciliation, parcel-charge reconciliation, SLA service-credit reconciliation, advertising spend-and-fee audit, contract-renewal audit, workforce timecard reconciliation, hotel booking-commission reconciliation, and warehouse cycle-count adjustment reconciliation products for autonomous agents. ## Output Returns a structured audit report including: overall verdict (e.g. MATCHED_WITHIN_TOLERANCE or DISPUTED), recommended disposition, observed and calculated availability in basis points, counted downtime seconds, expected vs observed credit in minor currency units, the credit tier selected, incident-level results, merged eligible intervals, risk flags (e.g. SERVICE_COMMITMENT_BREACHED, OVERLAPPING_ELIGIBLE_INCIDENTS_MERGED), evidence gaps, claim window status (OPEN/CLOSED), a SHA-256 report hash for integrity, and a claimBoundary object indicating whether funds or claims have moved. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "contract": { "type": "object", "required": [ "contractId", "contractVersion", "serviceId", "currency", "measurementPeriodStart", "measurementPeriodEnd", "serviceCommitmentBps", "minimumCountedOutageSeconds", "outageRoundingIncrementSeconds", "creditTiers", "maximumCreditMinor", "claimSubmissionWindowDays" ], "properties": { "currency": { "type": "string", "pattern": "^[A-Z]{3}$" }, "serviceId": { "type": "string", "maxLength": 120, "minLength": 1 }, "contractId": { "type": "string", "maxLength": 120, "minLength": 1 }, "creditTiers": { "type": "array", "items": { "type": "object", "required": [ "availabilityBelowBps", "creditBps" ], "properties": { "creditBps": { "type": "integer", "maximum": 10000, "minimum": 0 }, "availabilityBelowBps": { "type": "integer", "maximum": 10000, "exclusiveMinimum": 0 } }, "additionalProperties": false }, "maxItems": 50, "minItems": 1 }, "contractVersion": { "type": "string", "maxLength": 120, "minLength": 1 }, "maximumCreditMinor": { "anyOf": [ { "type": "integer", "maximum": 9007199254740991, "minimum": 0 }, { "type": "null" } ] }, "measurementPeriodEnd": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{1,3})?Z$" }, "serviceCommitmentBps": { "type": "integer", "maximum": 10000, "exclusiveMinimum": 0 }, "measurementPeriodStart": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{1,3})?Z$" }, "claimSubmissionWindowDays": { "type": "integer", "maximum": 365, "exclusiveMinimum": 0 }, "minimumCountedOutageSeconds": { "type": "integer", "maximum": 86400, "exclusiveMinimum": 0 }, "outageRoundingIncrementSeconds": { "type": "integer", "maximum": 86400, "exclusiveMinimum": 0 } }, "additionalProperties": false }, "auditPolicy": { "type": "object", "required": [ "evaluatedAt", "availabilityToleranceBps", "creditToleranceMinor" ], "properties": { "evaluatedAt": { "type": "string", "patter … (truncated) ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "summary": { "incidentCount": 2, "disputedIncidentCount": 0, "eligibleIncidentCount": 2, "mergedEligibleIntervalCount": 1 }, "verdict": "MATCHED_WITHIN_TOLERANCE", "contract": { "currency": "USD", "serviceId": "API-PRODUCTION", "contractId": "SLA-42", "contractVersion": "2026-07", "serviceCommitmentBps": 9990 }, "riskFlags": [ "OVERLAPPING_ELIGIBLE_INCIDENTS_MERGED", "SERVICE_COMMITMENT_BREACHED" ], "reportHash": "sha256-hex", "claimWindow": { "status": "OPEN", "submissionWindowDays": 30 }, "availability": { "varianceBps": 0, "totalPeriodSeconds": 86400, "countedDowntimeSeconds": 900, "observedAvailabilityBps": 9896, "calculatedAvailabilityBpsFloor": 9895, "calculatedAvailabilityBpsRounded": 9896 }, "evidenceGaps": [ "CALLER_SUPPLIED_CONTRACT_INCIDENT_AND_STATEMENT_FACTS_NOT_AUTHENTICATED" ], "claimBoundary": { "fundsMoved": false, "creditClaimFiled": false, "paymentAttempted": false, "providerMonitoringOrBillingStateVerified": false }, "schemaVersion": "SLA_SERVICE_CREDIT_AUDIT_V1", "serviceCredit": { "selectedTier": { "creditBps": 2500, "availabilityBelowBps": 9900 }, "varianceMinor": 0, "expectedCreditMinor": 25000, "observedCreditMinor": 25000, "eligibleServiceChargesMinor": 100000 }, "incidentResults": [], "countedIntervals": [], "requestCommitment": "sha256-hex", "providerStatementId": "STATEMENT-42", "recommendedDisposition": "MATCHED_NO_ACTION" } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sla-service-credit-audit-d7232eec/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from rooke-token-risk-pilot.rookepoole.workers.dev](https://www.zero.xyz/host/rooke-token-risk-pilot.rookepoole.workers.dev/llms.txt)