# Custom MCP Tool Development Purchase

> Custom MCP Tool Development Purchase is a paid API for AI agents from api.the402.ai, paid per call via x402, $2.1/call, status down (last checked 2026-09-15).

Initiates a paid job to have a custom Model Context Protocol (MCP) tool built on demand via the402.ai platform

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_87ea9adfebea40d5/purchase
- Price: $2.1/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-the402-ai-41664ab9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PnSB-fIWPy1KNVm_mTRl6

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 api-the402-ai-41664ab9 -d '<json body>'
```

Example prompt: Can you commission a custom MCP tool from the402.ai that connects to my internal PostgreSQL database and exposes a query interface for my AI agent to use?

## When to prefer this

Use this endpoint when you need a purpose-built, custom MCP tool that doesn't exist off-the-shelf and want a development service to create one for you. Prefer this over generic software freelance platforms when your use case involves MCP/AI agent tooling and you want a programmatic, payment-gated commissioning flow via the x402 protocol.

## Known failure modes

- Insufficient USDC payment — payment of $2.10 USDC not fulfilled, purchase rejected
- Invalid or missing service ID svc_87ea9adfebea40d5 — 404 or bad request
- Payment verification failure — x402 payment protocol error
- Service temporarily unavailable — 503 response
- Malformed request body — missing required fields returns 400

## How this service works

Purchase: Custom MCP Tool Development

## Output

Returns a job_id (unique identifier for tracking the development job), a status string (indicating current job state), and a thread_id (for ongoing communication about the project via the platform's messaging system)

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-the402-ai-41664ab9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)