# Animica Mesh Find — AI Service Discovery Search

> Animica Mesh Find — AI Service Discovery Search is a paid API for AI agents from animica.dev, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-13).

Searches the Animica x402 API mesh for services matching a plain-language goal description, returning ranked, callable service listings with pricing and demand data.

## Facts

- Endpoint: POST https://animica.dev/x402/mesh/find
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/animica-mesh-find-ai-service-discovery-search-06891c40
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k9sSUq9wocqHuX-BD1iWb

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 animica-mesh-find-ai-service-discovery-search-06891c40 -d '<json body>'
```

Example prompt: Search the Animica mesh for services that can translate text between languages — show me the top 5 results priced under $0.01 per call, and only include ones with a callable spec I can invoke right away.

## When to prefer this

Use this endpoint when an AI agent needs to dynamically discover which x402/micropayment-enabled APIs exist for a given task at runtime, especially when the agent does not already know the endpoint URL. It is the right choice when you want ranked, filtered, and optionally callable-only results with live demand and pricing signals from the Animica mesh. Prefer it over hardcoding service URLs or using a general web search when you need structured, machine-readable call specs and economic metadata (price, demand) to make an informed selection.

## Known failure modes

- Missing required 'goal' field returns a validation error
- Weights object with unrecognized keys may be silently ignored or cause a 400
- max_price_usd set extremely low may return zero results with an empty results array
- limit outside 1–50 range may return a validation error or be clamped
- Service may return stale demand data if index_age_seconds is high
- Network or index unavailability may return 5xx errors

## How this service works

Search the whole x402 economy and get a ranked shortlist of services that can do a job, within a budget. Merges Coinbase Bazaar and 402index into one index keyed by canonical resource URL, then answers the three questions a directory does not: CAN this be invoked (only about 5% publish a call spec, and that is a first-class field here, not something you infer from missing keys), is the price REAL (one live listing advertises ten billion dollars a call — implausible prices are excluded as bad data and reported, never silently rewritten), and is the demand real (total calls are trivially inflated by a merchant calling itself, so volume is credited only in proportion to distinct paying counterparties). Every result explains its own score, and the weights are returned so you can disagree with them. Lexical matching, no model: the same query against the same index ranks the same way.

## Output

A JSON object with a results array where each item contains the service resource URL, description, per-call price in USD, network, callability flag, a full call_spec for direct invocation, demand metrics (30-day call count, unique payers, concentration note), a relevance score, and a human-readable explanation of why it ranked where it did. Also includes the weights used for ranking, index-level statistics (total services indexed, how many are callable/priced/have demand, data age), and a caveats array noting any limitations or data quality issues.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "goal": {
   "type": "string",
   "description": "what you are trying to do, in plain words — matched against service descriptions"
  },
  "limit": {
   "type": "integer",
   "description": "how many results, 1..50 (default 10)"
  },
  "weights": {
   "type": "object",
   "description": "override the ranking weights {relevance, demand, price, callable}; they are normalised as given"
  },
  "max_price_usd": {
   "type": "number",
   "description": "exclude anything priced above this per call"
  },
  "require_callable": {
   "type": "boolean",
   "description": "only return services that publish a call spec you can invoke without guessing (default false)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/animica-mesh-find-ai-service-discovery-search-06891c40/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from animica.dev](https://www.zero.xyz/host/animica.dev/llms.txt)
