# QuantaFlow x402 API Gateway - Rapid TikTok Signer

> QuantaFlow x402 API Gateway - Rapid TikTok Signer is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Proxies requests to a TikTok signing/authentication service via the x402 micropayment protocol, returning signed TikTok API credentials or tokens per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-tiktok-signer-working?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapid-tiktok-signer-293f7074
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nUv-BOK7-LNDjQ0e2dQk3

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 quantaflow-x402-api-gateway-rapid-tiktok-signer-293f7074 -d '<json body>'
```

Example prompt: Sign this TikTok API request for me — use the rapid TikTok signer with path '/api/item/detail', method POST, and this query object: {itemId: '7123456789'} so I can make an authenticated call.

## When to prefer this

Choose this endpoint when you need per-call TikTok API request signing with crypto micropayments (x402/USDC), especially in web3-native or DeFi agent workflows where traditional API key management is impractical. Prefer this over managing your own TikTok signing infrastructure when you want pay-as-you-go access at $0.01 per call.

## Known failure modes

- Insufficient USDC balance causes payment failure and 402 response
- Invalid or malformed path parameter returns upstream error
- TikTok signer backend unavailable causes 502/504 passthrough
- Malformed JSON body causes request forwarding failure
- Unsupported HTTP method may result in upstream rejection
- Rate limiting from the upstream TikTok signer returns 429

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The upstream signed TikTok API response is passed through after successful x402 micropayment processing — typically includes authentication tokens, signed request headers, or raw TikTok API data depending on the path requested.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapid-tiktok-signer-293f7074/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)