# ForgeMesh Router - x402 Service Detail Lookup

> ForgeMesh Router - x402 Service Detail Lookup is a paid API for AI agents from router.forgemesh.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-18).

Retrieves detailed metadata for a specific x402 paid API service by its service ID, including URL, name, tags, health status, and reputation score.

## Facts

- Endpoint: GET https://router.forgemesh.io/api/services/%7Bid%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-router-x402-service-detail-lookup-88257c06
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d1dLSsqmaNs-lEBrJsNFY

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 forgemesh-router-x402-service-detail-lookup-88257c06
```

Example prompt: Can you pull up the full details for the x402 service with ID 'svc_weather_pro' on ForgeMesh — I want to see its URL, health status, and reputation score?

## When to prefer this

Use this endpoint when you already know the specific service ID and need full metadata for that service (URL, health, reputation, tags). Prefer the sibling search endpoint when you need to discover services by keyword, category, or tag without a known ID. This endpoint is ideal for validating a previously discovered service before invoking it or for resolving a service ID to its live URL in dynamic agent workflows.

## Known failure modes

- Service ID not found — returns 404 or empty result if the ID does not exist in the registry
- Stale data — health status or reputation score may lag behind real-time service availability
- Invalid ID format — malformed or placeholder IDs (e.g. '{id}' literally) return an error
- Payment failure — the $0.001 USDC x402 micropayment must succeed or the request is rejected
- Rate limiting — excessive calls may be throttled by the router

## How this service works

Coverage overview for ForgeMesh Router paid x402 API discovery.

## Output

Returns a JSON object with the service's unique ID, live URL, human-readable name, associated tags (e.g. 'weather', 'travel'), current health status (e.g. 'x402'), and a numeric reputation score (0–100) reflecting reliability and quality signals gathered by ForgeMesh.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "svc_example",
  "url": "https://example.com",
  "name": "Example x402 Service",
  "tags": [
   "weather",
   "travel"
  ],
  "health_status": "x402",
  "reputation_score": 87
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-router-x402-service-detail-lookup-88257c06/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from router.forgemesh.io](https://www.zero.xyz/host/router.forgemesh.io/llms.txt)