Back to Browse
Penny Engine — AI Agent Outcome Guard
x402
Penny Engine — AI Agent Outcome Guard is a paid API for AI agents from penny-paid-batch-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-19).
Validates AI agent outputs and CSV catalog data against defined expectations, returning a deterministic PASS/FAIL verdict with a SHA-256 fingerprint for audit.
Price / call$0.001
Success—
StatusUnknown
How this service works
Machine-to-machine result validation via x402. One structured call, deterministic PASS or FAIL and SHA-256 fingerprint, $0.001 USDC on Base.
Output
Returns a JSON object containing the goal type, a COMPLETED status, a SHA-256 fingerprint of the validated content, the number of workflow steps completed, and the service name. Each audited job or CSV batch receives a deterministic PASS or FAIL outcome backed by a cryptographic fingerprint for traceability.
Example use cases
Agent pipeline output quality gate
“I have 10 agent task results I need validated before they go downstream — run an agent-output-batch-qa audit on them against these expectations and tell me which ones pass and which fail, plus the fingerprint.”
Product catalog CSV compliance audit
“Can you audit this product catalog CSV using catalog-csv-audit mode and tell me if it passes validation? I need the fingerprint for our records.”
Margin-sensitive catalog review
“Run a catalog-csv-audit on this CSV and check it against a target margin of 30% — I need a PASS or FAIL and the SHA-256 hash so I can certify the results.”
Technical details
Endpoint
POSThttps://penny-paid-batch-production.up.railway.app/api/fulfill?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a deterministic, cryptographically verifiable PASS/FAIL verdict on AI agent job outputs or CSV catalog data — especially in automated pipelines where auditability and fingerprinting matter. Prefer it over ad-hoc LLM-based evaluation when you need reproducible, machine-to-machine validation with a tamper-evident SHA-256 hash, or when you need to batch-QA up to 20 agent results in a single call for under a tenth of a cent.
Side effects
- Invalid goal enum value causes rejection — must be exactly 'catalog-csv-audit' or 'agent-output-batch-qa'
- Jobs array below minItems (1) or above maxItems (20) triggers validation error
- Missing required job fields (id, result, expectations) cause schema rejection
- Malformed CSV string may produce unexpected audit failure
- Payment failure via x402 protocol blocks fulfillment
- Overly large or complex job objects may exceed processing limits
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| goal | string | |
| input | object | |
| maxPriceUsd | number |
Output
Schema · Response
{
"type": "json",
"example": {
"goal": "catalog-csv-audit",
"status": "COMPLETED",
"service": "M2M Unified Fulfillment",
"evidence": {
"algorithm": "SHA-256"
},
"workflow": {
"stepsCompleted": 3
}
}
}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"