HTTP batching

An HTTP round-trip to api.numeraire.dev is ~30-80 ms depending on region. If you’re pricing 50 swaps, 50 sequential round-trips ≈ 2-4 s of wall-clock from network alone — almost all of which is wasted, because the actual pricing work is sub-millisecond per swap.

POST /pricing/batch collapses N pricing requests into one HTTP call:

• One round-trip for N positions × M request-types.
• Server fans out across the JAX kernel internally; per-slot errors don’t fail the whole batch.
• Per-slot request_id field lets you correlate each result back to its caller-side identifier (Excel cell address, spreadsheet row, etc.).

→ When to batch vs. single endpoint, batch-size limits, per-slot error handling — full guide coming in v1.3.