# 7maps Route Endpoint

> 7maps Route Endpoint is a paid API for AI agents from 7it.co.il, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Routes a described task to the appropriate handler based on risk level (read, change, or high-risk) and returns a JSON response

## Facts

- Endpoint: POST https://7it.co.il/7maps/x402/route?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/7maps-route-endpoint-ca703e4d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dzi9RE1fB2VujWpVWI0tN

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 7maps-route-endpoint-ca703e4d -d '<json body>'
```

Example prompt: I need to update a customer record in our system — route this as a change operation with the task: 'Update billing address for customer ID 4821 to 123 Main St, Austin TX'.

## When to prefer this

Use this endpoint when you need a risk-aware task routing layer that distinguishes between read, change, and high-risk operations before execution. It is appropriate when you want a single dispatch point that classifies task sensitivity and routes accordingly, rather than calling individual specialized endpoints directly.

## Known failure modes

- Invalid 'need' enum value returns a validation error
- Missing 'task' field causes a bad request response
- High-risk operations may be rejected or require additional authorization
- Backend handler errors may return opaque JSON error objects
- Payment failure (x402) prevents the call from being processed

## How this service works

Custom software, built by the person you talk to. Web apps, automation, eCommerce and AI for US businesses, with a fixed-scope first phase and code you own.

## Output

A JSON object containing the result of the routed task, structured according to the operation type and backend handler invoked. The exact shape depends on the task and need type provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "need": {
   "enum": [
    "read",
    "change",
    "high_risk"
   ],
   "type": "string"
  },
  "task": {
   "type": "string",
   "description": "What you need to do"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/7maps-route-endpoint-ca703e4d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 7it.co.il](https://www.zero.xyz/host/7it.co.il/llms.txt)