# TiresAPI Free-Form Data Request

> TiresAPI Free-Form Data Request 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 free-form, ad-hoc data request to the TiresAPI data team for manual triage and out-of-band fulfillment, covering asks like adding retailer coverage or backfilling historical pricing.

## Facts

- Endpoint: POST https://tiresapi.com/api/v1/requests/data
- 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-310e0829
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RJJQj5yYV_C3BWgVQAazL

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-310e0829 -d '<json body>'
```

Example prompt: Submit a data request to TiresAPI asking them to add support for retailer Discount Tire Direct and backfill historical pricing for SKU key_brand_mpc=MICH-P215-65R17-94T — this doesn't fit the standard inventory or pricing endpoints.

## When to prefer this

Use this endpoint when your data need doesn't map to any existing TiresAPI endpoint — specifically when you want to request new retailer coverage, backfill historical SKU pricing, or flag any ad-hoc gap in the dataset. Do not use this for real-time inventory lookups, price history queries, or SQL sandbox queries — those have dedicated endpoints.

## Known failure modes

- Missing or empty request body — returns 400 Bad Request
- Authentication or payment failure — returns 402 or 401
- Service unavailable — returns 503 if queue is down
- Malformed JSON payload — returns 400 with validation error

## How this service works

Submit a free-form data request. Always queued; the data team triages and replies out-of-band. Use for ad-hoc asks that don't fit retailer-coverage (e.g. "add support for retailer X" or "backfill historical pricing for sku Y").

## Output

Returns a queued request confirmation, typically including a request ID or acknowledgement that the data team has received the free-form request and will triage and respond out-of-band.

## Example request

```json
{
 "notes": "Test request for QA validation of data request submission endpoint",
 "free_form": "Please add retailer coverage for Discount Tire Direct and backfill historical pricing data for tire SKU MICH-P215-65R17-94T. This data is needed for our inventory reconciliation project."
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "notes": {
   "type": "string",
   "maxLength": 2000
  },
  "free_form": {
   "type": "string",
   "maxLength": 8000,
   "minLength": 4,
   "description": "Free-form request text. 4–8000 characters."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "notes": "Request queued for the data team to triage.",
  "status": "queued",
  "amount_usd": "0.010",
  "request_id": 4013,
  "request_type": "general_request"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tiresapi-com-310e0829/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)