# IntentFlow Context Relay

> IntentFlow Context Relay is a paid API for AI agents from intentflow.melis.ai, paid per call via x402, $0.001000/call, status down (last checked 2026-09-15).

Relays a natural language intent instruction to a target agent via a paid context relay channel

## Facts

- Endpoint: POST https://intentflow.melis.ai/relay
- Price: $0.001000/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/intentflow-melis-ai-49279548
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2r3MWPYyFsFC64JAHswdx

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 intentflow-melis-ai-49279548 -d '<json body>'
```

Example prompt: Relay this instruction to the target agent: 'Summarize the top 3 headlines from today's tech news and return them as bullet points.'

## When to prefer this

Use this endpoint when you need to relay a natural language instruction from one agent to another in a multi-agent pipeline and are willing to pay per-relay. It is particularly suited for agentic orchestration workflows where a lightweight, pay-per-use context bridge is needed rather than a persistent message queue or subscription-based broker.

## Known failure modes

- Missing or empty 'intent' field returns a 400 validation error
- Payment not provided or insufficient USDC results in a 402 payment required error
- Target agent unavailable or unreachable returns a relay failure or timeout
- Malformed request body causes a 422 unprocessable entity error
- Network or infrastructure issues may result in a 503 service unavailable response

## How this service works

IntentFlow: $0.001 per context relay

## Output

The relay confirms the intent was forwarded to the target agent and returns the agent's response or an acknowledgment of the relayed context.

## Example request

```json
{
 "intent": "Please acknowledge receipt of this test message and confirm that the relay channel is functioning properly."
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "intent": {
   "type": "string",
   "description": "Natural language instruction for the target agent"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "relay_id",
  "retrieve_url",
  "target_agent",
  "context_bundle_hash",
  "estimated_delivery_ms"
 ],
 "properties": {
  "status": {
   "type": "string"
  },
  "relay_id": {
   "type": "string"
  },
  "retrieve_url": {
   "type": "string"
  },
  "target_agent": {
   "type": "string"
  },
  "context_bundle_hash": {
   "type": "string"
  },
  "estimated_delivery_ms": {
   "type": "number"
  }
 }
}
```

## More

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