# Bounty Engineer Funding Rates Snapshot API

> Bounty Engineer Funding Rates Snapshot API is a paid API for AI agents from bounty-engineer-x402-prod.onrender.com, paid per call via x402, $0.0075/call, status unknown (last checked 2026-10-12).

Fetches and compares perpetual futures funding rates for a given trading symbol across Binance and Bybit, returning a snapshot with per-provider rates and the spread between them.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/funding-rates?utm_source=zero.xyz
- Price: $0.0075/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-funding-rates-snapshot-api-aba6d595
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tPczW8qBGCpluRHS_T32F

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 bounty-engineer-funding-rates-snapshot-api-aba6d595 -d '<json body>'
```

Example prompt: What are the current funding rates for BTCUSDT on both Binance and Bybit, and what's the spread between them?

## When to prefer this

Use this endpoint when you need a fast, cross-exchange funding rate snapshot for perpetual futures markets and want the spread computed automatically. Ideal for agents running arbitrage detection, pre-trade cost analysis, or position management workflows where funding rates on Binance and/or Bybit specifically are required. Prefer this over building direct exchange API calls when you need a normalized, machine-payable ($0.001 USDC) single-call comparison.

## Known failure modes

- Invalid symbol format (must match ^[A-Za-z0-9_/-]{5,24}$) returns validation error
- Symbol not found on one or both providers — that provider's ok field returns false
- Provider API downtime causes partial or full failure with ok:false for affected providers
- Too many providers specified (max 2) returns schema validation error
- Payment failure (x402 protocol) returns 402 Payment Required

## How this service works

Machine-buyable infrastructure for autonomous agents: API cost routing, margin optimization, funding-rate data, webpage extraction, result verification, spend controls, retry planning, state, tender search and GitHub bounty intelligence.

## Output

Returns a JSON object with ok status, mode identifier, the queried symbol, an array of per-provider results (each with provider name, ok flag, and funding_rate as a decimal), a fetched_at ISO timestamp, the spread_rate (difference between providers), and provider_count. Example: Binance 0.0001, Bybit 0.00008, spread 0.00002.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "symbol": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_/-]{5,24}$"
  },
  "providers": {
   "type": "array",
   "items": {
    "enum": [
     "binance",
     "bybit"
    ],
    "type": "string"
   },
   "maxItems": 2
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "funding_rates_snapshot",
  "symbol": "BTCUSDT",
  "providers": [
   {
    "ok": true,
    "provider": "binance",
    "funding_rate": 0.0001
   },
   {
    "ok": true,
    "provider": "bybit",
    "funding_rate": 0.00008
   }
  ],
  "fetched_at": "2026-09-30T00:00:00.000Z",
  "spread_rate": 0.00002,
  "provider_count": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-funding-rates-snapshot-api-aba6d595/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-engineer-x402-prod.onrender.com](https://www.zero.xyz/host/bounty-engineer-x402-prod.onrender.com/llms.txt)