# Intent-to-Endpoint Matchmaker API

> Intent-to-Endpoint Matchmaker API is a paid API for AI agents from intent-api-matchmaker-mainnet-production.up.railway.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Matches normalized agent intents to the most fitting endpoint contracts, returning ranked results with explainable fit scores and constraints.

## Facts

- Endpoint: POST https://intent-api-matchmaker-mainnet-production.up.railway.app/v1/match
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/intent-to-endpoint-matchmaker-api-e6afad05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_174C7Mb0eaAcgbU3efKr2

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 intent-to-endpoint-matchmaker-api-e6afad05 -d '<json body>'
```

Example prompt: I have a list of 5 normalized agent intents and 20 candidate endpoint contracts — can you match each intent to up to 3 endpoints, only returning results with a fit score above 0.7, and explain why each match fits?

## When to prefer this

Choose this endpoint when an AI agent needs to dynamically route normalized intents to the best-fitting API contracts from a candidate set, especially when explainability of the match is important. Prefer it over static routing tables or manual API selection when the intent space is large or variable. Best suited for orchestration layers, agent frameworks, and API marketplaces that need scored, ranked, and explainable endpoint recommendations at runtime.

## Known failure modes

- Intents array is empty or exceeds 100 items — validation error returned
- Endpoints array is empty or exceeds 100 items — validation error returned
- Raw prompts or user identities passed as intents instead of normalized form — rejected by schema
- minimumFitScore outside 0–1 range — validation error
- limitPerIntent outside 1–10 range — validation error
- No endpoints meet the minimumFitScore threshold — empty matches array returned
- Payment not provided or insufficient — x402 payment required response

## How this service works

Match normalized agent intents to endpoint contracts with explainable constraints.

## Output

A ranked list of endpoint matches per intent, each including a fit score (0–1), the matched endpoint contract details, and explainable constraints describing why the endpoint was selected or deprioritized. Results are filtered by minimumFitScore and capped at limitPerIntent matches per intent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "intents": {
   "type": "array",
   "maxItems": 100,
   "minItems": 1,
   "description": "Normalized agent intents; raw prompts and identities are not accepted."
  },
  "endpoints": {
   "type": "array",
   "maxItems": 100,
   "minItems": 1
  },
  "limitPerIntent": {
   "type": "integer",
   "maximum": 10,
   "minimum": 1
  },
  "minimumFitScore": {
   "type": "number",
   "maximum": 1,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/intent-to-endpoint-matchmaker-api-e6afad05/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intent-api-matchmaker-mainnet-production.up.railway.app](https://www.zero.xyz/host/intent-api-matchmaker-mainnet-production.up.railway.app/llms.txt)