# 100BTC Public LLM Models Catalog Lookup

> 100BTC Public LLM Models Catalog Lookup is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Searches and lists publicly available LLM models from the OpenRouter public model catalog via a pay-per-call API

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/public-llm-models?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-public-llm-models-catalog-lookup-2ce9de5a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_McSXHnN1zg0brqKsBYfgf

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 100btc-public-llm-models-catalog-lookup-2ce9de5a -d '<json body>'
```

Example prompt: Search the OpenRouter public model catalog for LLM models related to 'code generation' and show me up to 10 results.

## When to prefer this

Choose this endpoint when you need to programmatically discover or search the OpenRouter public model catalog without maintaining your own model list. It is ideal for agents that need to dynamically resolve which LLM models are available before selecting one, and it costs only $0.01 USDC per call via the x402 micropayment protocol. Prefer alternatives if you need real-time inference latency benchmarks, private/non-public model listings, or model metadata beyond what OpenRouter's public catalog exposes.

## Known failure modes

- Empty models array returned if no results match the query
- OpenRouter catalog fetch fails causing a non-200 or error response
- Payment not processed (HTTP 402 returned before data is delivered)
- Query exceeds 100 character limit causing validation error
- Limit outside 1–20 range causing schema validation rejection

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

Returns a JSON object containing a list of public LLM models from the OpenRouter catalog, the source label ('OpenRouter public model catalog'), a status string (e.g. 'RESULTS'), a product code ('EXP-23'), and a measurement scope note clarifying this reflects catalog fetch latency only — not model inference latency.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "maximum": 20,
   "minimum": 1
  },
  "query": {
   "type": "string",
   "maxLength": 100
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "models": [],
  "source": "OpenRouter public model catalog",
  "status": "RESULTS",
  "product": "EXP-23",
  "measurement_scope": "catalog HTTP fetch only; not model inference latency"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-public-llm-models-catalog-lookup-2ce9de5a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)