# Bounty Engineer Rate Limit Plan

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

Generates a scheduled batch plan for distributing a set number of API requests across time, respecting per-minute and per-hour rate limits.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/rate-limit-plan?utm_source=zero.xyz
- Price: $0.002/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-rate-limit-plan-1d28244b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-gXAPKEZkBs0X4T1zcdbT

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-rate-limit-plan-1d28244b -d '<json body>'
```

Example prompt: I need to send 180 API requests starting at 2026-10-02T23:49:45Z, with a limit of 60 per minute — can you generate a batch schedule that spaces them out correctly?

## When to prefer this

Use this endpoint when an autonomous agent or workflow needs to pre-compute a time-phased dispatch schedule for a large number of API calls subject to rate-limit constraints. It is ideal when you need deterministic scheduling output (exact timestamps per batch) rather than dynamic throttling at runtime. Prefer this over ad-hoc sleep/retry logic when you want auditable, upfront batch plans.

## Known failure modes

- Missing or invalid integer fields (per_minute, requests) may cause plan computation failure
- Conflicting rate constraints (per_minute and per_hour both set to very low values) may produce unexpected truncation
- start_at in invalid ISO format returns a parse error
- Requests value of 0 or negative integer may return empty batch array or error
- Payment failure via x402 protocol results in 402 response before plan is generated

## 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 an array of batches, each with a batch number, request count, and ISO 8601 scheduled timestamp. Also includes total request count, total batch count, effective per-minute rate, remaining unscheduled requests, and a truncation flag indicating whether all requests fit within the plan.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "per_hour": {
   "type": "integer"
  },
  "requests": {
   "type": "integer"
  },
  "start_at": {
   "type": "string"
  },
  "per_minute": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "rate_limit_plan",
  "batches": [
   {
    "batch": 1,
    "requests": 60,
    "scheduled_at": "2026-10-11T16:11:46.721Z"
   },
   {
    "batch": 2,
    "requests": 60,
    "scheduled_at": "2026-10-11T16:12:46.721Z"
   },
   {
    "batch": 3,
    "requests": 60,
    "scheduled_at": "2026-10-11T16:13:46.721Z"
   }
  ],
  "requests": 180,
  "truncated": false,
  "batch_count": 3,
  "remaining_requests": 0,
  "effective_per_minute": 60
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-rate-limit-plan-1d28244b/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)