Batch Result Summary
by Batch Result Summary in Onchain & crypto
Batch Result Summary: summarizes success, failure, pending, and unknown batch statuses using only bounded caller-supplied values. Call when you need a bounded batch result summary result before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bounded transformation or validation finding with counts, normalized values, and a versioned result contract for Batch Result Summary as versioned deterministic JSON. Price: $0.001 USDC via x402 on B…
https://api.delx.ai/api/v1/x402/batch-result-summary- Price
- $0.001
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 22 ms
- 1.4 s slowest 5%
- Last check
- Passed
- 26 min ago, next in 2 min
Reliability
How to call it
POST https://api.delx.ai/api/v1/x402/batch-result-summary
Each call costs $0.001 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.delx.ai/api/v1/x402/batch-result-summary
content-type: application/json
{
"results": [
{
"id": "a",
"status": "success"
},
{
"id": "b",
"status": "failed"
}
]
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
results | array of object | Yes | Results supplied to Batch Result Summary; used only for this bounded calculation and processed in memory without retention. |
Example response
The provider's example. We can't check it without paying.
{
"evidence": {
"external_calls": 0,
"input_sha256": "6466dae814565dd9a275c1d144bdf845f9e6540fdff3d4cc58ef98e81c899637",
"retained": false
},
"operation": "data_batch:batch_result_summary",
"result": {
"counts": {
"failed": 1,
"pending": 0,
"success": 1,
"unknown": 0
},
"total": 2
},
"schema": "delx/util-batch-result-summary/v1",
"status": "pass"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.delx.ai/api/v1/x402/batch-result-summary' \
-H 'content-type: application/json' \
--data-raw '{"results":[{"id":"a","status":"success"},{"id":"b","status":"failed"}]}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.delx.ai/api/v1/x402/batch-result-summary' \
-H 'content-type: application/json' \
--data-raw '{"results":[{"id":"a","status":"success"},{"id":"b","status":"failed"}]}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.delx.ai%2Fapi%2Fv1%2Fx402%2Fbatch-result-summary&method=POST
const res = await pay("https://api.delx.ai/api/v1/x402/batch-result-summary", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"results": [
{
"id": "a",
"status": "success"
},
{
"id": "b",
"status": "failed"
}
]
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.delx.ai/api/v1/x402/batch-result-summary",
json={
"results": [
{
"id": "a",
"status": "success",
},
{
"id": "b",
"status": "failed",
},
],
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 26 min ago | Passed | 402 | 27 ms | $0.001 |
| 4 h ago | Passed | 402 | 33 ms | $0.001 |
| 9 h ago | Passed | 402 | 39 ms | $0.001 |
| 13 h ago | Passed | 402 | 19 ms | $0.001 |
| 17 h ago | Passed | 402 | 22 ms | $0.001 |
Show 10 older checks
| 22 h ago | Passed | 402 | 25 ms | $0.001 |
| 26 h ago | Passed | 402 | 20 ms | $0.001 |
| 30 h ago | Passed | 402 | 67 ms | $0.001 |
| 34 h ago | Passed | 402 | 1.4 s | $0.001 |
| 38 h ago | Passed | 402 | 52 ms | $0.001 |
| 42 h ago | Passed | 402 | 136 ms | $0.001 |
| 46 h ago | Passed | 402 | 1.8 s | $0.001 |
| 2 days ago | Passed | 402 | 10 ms | $0.001 |
| 2 days ago | Passed | 402 | 29 ms | $0.001 |
| 2 days ago | Passed | 402 | 75 ms | $0.001 |