Back to Browse
Delx Commerce — Agent Delivery SLA Check
x402
Delx Commerce — Agent Delivery SLA Check is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).
Validates whether an agent task delivery meets SLA requirements by checking success, completion, and latency against a maximum threshold.
Price / call$0.001
Success—
StatusUnknown
How this service works
Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.
Output
Returns a JSON object with a result block containing success, accepted, complete, and latency_within_sla booleans; a top-level status field ('pass' or 'fail'); and an evidence block with a SHA256 hash of the input, a retained=false flag confirming no data is stored, and a count of external calls made (always 0), plus the operation name for auditability.
Example use cases
Post-task SLA compliance check
“My agent just finished a task — it succeeded and completed in 420ms. The contract allows up to 600ms. Did it pass SLA?”
Failed delivery investigation
“A task came back as not successful and took 850ms against a 500ms SLA limit — can you check if this delivery was accepted or failed the contract?”
Borderline latency audit
“I need to verify if a completed, successful delivery that took exactly 500ms passes when the maximum allowed latency is also 500ms — run the SLA check for me.”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/agent-delivery-sla-check?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a lightweight, auditable, cryptographically-evidenced SLA compliance check for an agent task delivery without storing any input data. It is ideal when you need a verifiable on-chain-payable micro-check (0.001 USDC) that produces a tamper-evident SHA256 evidence hash confirming inputs were not retained, making it suitable for delivery contracts between autonomous agents.
Side effects
- Missing required fields (success, complete, latency_ms, maximum_latency_ms) may result in a validation error
- Non-integer latency values may cause a schema rejection
- Payment failure via x402 protocol will block the call before processing
- If maximum_latency_ms is zero or negative the result may be undefined
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| success | boolean | Success supplied to Agent Delivery Sla Check; used only for this bounded calculation and processed in memory without retention. |
| complete | boolean | Complete supplied to Agent Delivery Sla Check; used only for this bounded calculation and processed in memory without retention. |
| latency_ms | integer | Latency Ms supplied to Agent Delivery Sla Check; used only for this bounded calculation and processed in memory without retention. |
| maximum_latency_ms | integer | Maximum Latency Ms supplied to Agent Delivery Sla Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"success": true,
"accepted": true,
"complete": true,
"latency_within_sla": true
},
"schema": "delx/util-agent-delivery-sla-check/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "5691ee4b6d16e4b15b7baaa5b8e6210515ab50f12f536eb022ca6f4055737b1f",
"external_calls": 0
},
"operation": "delivery_contract:agent_delivery_sla_check"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"