# Tanship PayAI — Durable Rate Limit Check

> Tanship PayAI — Durable Rate Limit Check is a paid API for AI agents from x402.tanship.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-15).

Checks whether a named rate limit slot is currently allowed or blocked, using a durable (persistent) rate limiter, gated by USDC micropayment via x402.

## Facts

- Endpoint: POST https://x402.tanship.dev/v1/durable/ratelimit/check?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanship-payai-durable-rate-limit-check-cd037f0c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aIQwfQ7hvEjeT7RRGVE-q

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 tanship-payai-durable-rate-limit-check-cd037f0c -d '<json body>'
```

Example prompt: Check whether the rate limit for my current request is still within bounds — use the Tanship durable rate limit checker and let me know if the call should be allowed or blocked.

## When to prefer this

Use this endpoint when you need a persistent, durable rate limit check that survives restarts and is shared across distributed agent instances — particularly when enforcing usage caps before calling expensive or sensitive downstream APIs. Prefer this over in-memory rate limiters when consistency and durability across calls matter, and when you're already operating in a payment-gated x402 workflow on Base.

## Known failure modes

- Payment not provided or insufficient USDC — returns HTTP 402 with x402 payment requirements
- Malformed input body or missing required fields — returns 400 bad request
- Rate limit key not found or not configured — may return an error or a default allow/block state
- Network timeout reaching the durable backend — returns 5xx error
- Invalid bodyType enum value — rejected at schema validation

## How this service works

Payment-gated AI and browser automation API using the x402 protocol. All /v1/* endpoints require USDC payment on Base (eip155:8453) via x402 v2 exact scheme.

## Output

Returns a decision on whether the checked rate limit slot is currently allowed or blocked, along with details such as remaining request quota and when the limit resets, enabling agents to gate downstream actions accordingly.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanship-payai-durable-rate-limit-check-cd037f0c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.tanship.dev](https://www.zero.xyz/host/x402.tanship.dev/llms.txt)