# CIEL M2M API Marketplace - Compute Provider

> CIEL M2M API Marketplace - Compute Provider is a paid API for AI agents from 169.58.38.67.sslip.io, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-18).

Dispatches a compute job to one of 50+ AI-agent micro-services (data parsing, crypto analytics, security scanning, code tools) via a single POST endpoint, billed per call in USDC on Base via x402.

## Facts

- Endpoint: POST https://169.58.38.67.sslip.io/api/compute-provider
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ciel-m2m-api-marketplace-compute-provider-852ac661
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vyDovjW7T21sMBTqnOK-9

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 ciel-m2m-api-marketplace-compute-provider-852ac661 -d '<json body>'
```

Example prompt: Run a crypto analytics job on wallet address 0xABC123 through the CIEL M2M compute provider and return the on-chain activity summary — I'll pay the $0.15 USDC fee via x402.

## When to prefer this

Choose this endpoint when your agent needs to dynamically dispatch to one of many heterogeneous compute tasks (parsing, analytics, security, code) without managing multiple API keys, and when pay-per-call micropayment billing via x402 USDC on Base is acceptable or preferred over subscription billing. It is especially useful in autonomous agent pipelines where the task type varies per invocation.

## Known failure modes

- Payment declined or insufficient USDC balance — x402 payment handshake fails before compute executes
- Malformed or missing 'properties' field — service returns 400 with schema validation error
- Unsupported or unrecognized service selector — endpoint returns an error indicating no matching micro-service
- Timeout on long-running compute jobs — response may not arrive within agent polling window
- Raw IP / sslip.io hostname TLS issues — some clients may reject the self-signed or sslip certificate

## How this service works

50+ micro-services for AI agents: data parsing, crypto analytics, security scanning, code tools, and more. Pay per call via x402 (USDC on Base) or RapidAPI subscription.

## Output

Returns a JSON object containing the result of the dispatched compute job — structure varies by micro-service called, but the envelope is {"result": <data>}. May include parsed records, analytics metrics, scan findings, or code execution output depending on the service invoked.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "data"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ciel-m2m-api-marketplace-compute-provider-852ac661/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 169.58.38.67.sslip.io](https://www.zero.xyz/host/169.58.38.67.sslip.io/llms.txt)