Back to Browse
Delx Commerce — Agent Delivery Acceptance Gate
x402
Delx Commerce — Agent Delivery Acceptance Gate 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 acceptance criteria (completeness, SLA, schema validity, payment match, and provenance) and returns a pass/fail gate decision.
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 the gate decision (accepted: true/false), a breakdown of each check (complete, within_sla, schema_valid, payment_match, provenance_present), a list of any failed checks, overall status (pass/fail), and evidence including the input SHA-256 hash and a flag confirming no data was retained.
Example use cases
Gating agent output before payment release
“Before I release payment for this agent task, verify it passes all acceptance checks — it's marked complete, delivered within SLA, the schema is valid, payment matches, and provenance is present.”
Automated QA gate in an agent pipeline
“I need to run an acceptance gate on this delivery result from my agent: it's complete and schema-valid, but I'm not sure if it's within SLA or has provenance — can you check all the criteria and tell me what failed?”
Auditing a rejected delivery
“This agent delivery was rejected — can you run it through the acceptance gate with complete=true, within_sla=false, schema_valid=true, payment_match=true, provenance_present=false, and show me exactly which checks failed?”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/agent-delivery-acceptance-gate?utm_source=zero.xyzWhen to prefer
Use this endpoint when an AI agent needs a lightweight, verifiable, cryptographically-evidenced gate to decide whether a delivered task result should be accepted — especially in pay-per-result pipelines where you need to confirm completeness, SLA adherence, schema validity, payment alignment, and provenance before releasing funds or proceeding. Prefer this over custom logic when you need a tamper-evident audit trail (SHA-256 evidence hash) with no data retention.
Side effects
- Missing or malformed boolean fields cause validation to fail unexpectedly
- All checks must be explicitly provided; omitted fields may default to false and fail the gate
- Payment issues (402) if USDC micropayment via x402 is not properly attached
- Ambiguous delivery state if caller passes inconsistent flag combinations
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| complete | boolean | Complete supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention. |
| within_sla | boolean | Within Sla supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention. |
| schema_valid | boolean | Schema Valid supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention. |
| payment_match | boolean | Payment Match supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention. |
| provenance_present | boolean | Provenance Present supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"checks": {
"complete": true,
"within_sla": true,
"schema_valid": true,
"payment_match": true,
"provenance_present": true
},
"accepted": true,
"failed_checks": []
},
"schema": "delx/util-agent-delivery-acceptance-gate/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "944e4ad49cea825f997892500c55a26a4a6935b658218b3de892e1c5bee11f68",
"external_calls": 0
},
"operation": "delivery_contract:agent_delivery_acceptance_gate"
}
}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"