# TiresAPI Retailer-Coverage Request Submission

> TiresAPI Retailer-Coverage Request Submission is a paid API for AI agents from tiresapi.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Submits a request to expand retailer coverage for a given retailer and ZIP code combination, logging it for analytics and crediting back $0.01 if the combo is already covered.

## Facts

- Endpoint: POST https://tiresapi.com/api/v1/requests/retailer-coverage
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tiresapi-com-6bb15125
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iljzcxEUU0nm8FIK64C-v

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 tiresapi-com-6bb15125 -d '<json body>'
```

Example prompt: Submit a retailer-coverage request to TiresAPI for Discount Tire in ZIP code 78701 — I want to make sure that retailer-ZIP combo is being tracked even if it's already covered.

## When to prefer this

Use this endpoint when you want to signal to TiresAPI that a specific retailer-ZIP combination should be added to or confirmed in their coverage network. Ideal for agents that have encountered a coverage gap during inventory or price lookups and want to proactively request expansion. The built-in credit-back mechanism makes it safe to call even for already-covered combos, so agents can use it both as a coverage gap signal and as a coverage verification step without financial risk.

## Known failure modes

- Invalid or unrecognized retailer identifier — returns 400 with retailer validation error
- Malformed or non-existent ZIP code — returns 400 with ZIP validation error
- Insufficient virtual balance to cover the $0.01 fee — returns 402 payment required
- Rate limiting or quota exceeded — returns 429
- Service unavailable or timeout — returns 503

## How this service works

Submit a retailer-coverage request. If we already cover the (retailer, zip) combo the row is still logged for analytics AND the $0.01 is credited back to the agent's virtual balance — so agents aren't out of pocket for a useful-but-already-served signal.

## Output

A confirmation that the retailer-ZIP coverage request was logged for analytics. If the combination was already covered, the $0.01 call cost is credited back to the agent's virtual balance. Returns the coverage status (new vs. already-served) and any relevant request ID or log entry.

## Example request

```json
{
 "notes": "QA test for retailer coverage tracking in Austin TX area",
 "zip_code": "78701",
 "retailer_key": "DISCOUNT_TIRE"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "notes": {
   "type": "string",
   "maxLength": 2000
  },
  "zip_code": {
   "type": "string",
   "pattern": "^[0-9]{5}$"
  },
  "retailer_key": {
   "type": "string",
   "maxLength": 100,
   "description": "Uppercase scraper key."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "queued",
  "request_id": 4012,
  "credited_usd": null
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tiresapi-com-6bb15125/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tiresapi.com](https://www.zero.xyz/host/tiresapi.com/llms.txt)