# 2s Batch Run — Multi-Endpoint Batch Executor

> 2s Batch Run — Multi-Endpoint Batch Executor is a paid API for AI agents from 2s.io, paid per call via x402, $0.0025/call, status unknown (last checked 2026-09-14).

Execute 1–50 sub-calls across 2s.io's ground-truth data endpoints in a single batched HTTP request, paying per sub-call in USDC via x402.

## Facts

- Endpoint: POST https://2s.io/api/batch/run
- Price: $0.0025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/2s-batch-run-multi-endpoint-batch-executor-a6208df8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Gctg4pmMZAY63w4WboYU7

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 2s-batch-run-multi-endpoint-batch-executor-a6208df8 -d '<json body>'
```

Example prompt: I need to run three lookups at once — decode VIN 1HGBH41JXMN109186, look up the crypto price for ETH, and do a public records search for John Smith in California — can you batch all three sub-calls together into one 2s.io batch/run request?

## When to prefer this

Use this endpoint when you need to invoke multiple 2s.io sub-endpoints in a single round-trip to reduce latency and simplify payment — instead of making separate HTTP calls for each. Ideal for AI agent pipelines that need to fan out across domains (e.g. finance + public records + geo) and aggregate results. Not suitable if you only need a single endpoint call, in which case using the individual endpoint directly may be simpler.

## Known failure modes

- One or more sub-calls fail (individual item ok=false) while others succeed — partial success is possible
- Exceeds 50 sub-calls limit — request rejected
- Invalid or unknown endpoint dotted-id in a sub-call — that item returns error
- Insufficient USDC balance or x402 payment failure — entire batch rejected
- Malformed params object for a sub-call — that item returns validation error

## How this service works

The (most) everything API: 575+ pay-per-call endpoints for AI agents — ground-truth data, a full AI gateway, and agent infrastructure (storage, queues, watchers). USDC via x402, no signup, no API keys, and upto billing: pay actual usage, not the quote.

## Output

Returns a JSON object with an 'ok' boolean, a 'meta' block containing the call count and total_price_usd, and an 'items' array where each element has its own 'ok' flag, the 'endpoint' dotted-id that was called, the 'data' object with that sub-call's response payload, and the individual 'price_usd' charged for that sub-call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "calls": {
   "type": "array",
   "description": "1–50 sub-calls, each { endpoint: dotted-id, params: object }."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/2s-batch-run-multi-endpoint-batch-executor-a6208df8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2s.io](https://www.zero.xyz/host/2s.io/llms.txt)