# Mangrove AI Copilot - Start New Conversation

> Mangrove AI Copilot - Start New Conversation is a paid API for AI agents from api.mangrovedeveloper.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-04).

Starts a new AI copilot conversation session within the Mangrove Developer platform for developer assistance, API guidance, and MCP/AI integration support.

## Facts

- Endpoint: POST https://api.mangrovedeveloper.ai/api/v1/ai-copilot/start_new_conversation?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mangrove-ai-copilot-start-new-conversation-d9489ff7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W9Rvzunt-V60UdKohp3bn

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 mangrove-ai-copilot-start-new-conversation-d9489ff7 -d '<json body>'
```

Example prompt: Start a new conversation with the Mangrove AI copilot so I can ask it questions about setting up MCP integrations and Mangrove Agent API contracts.

## When to prefer this

Choose this endpoint when you need to initiate a fresh AI-assisted developer support session specifically within the Mangrove Developer ecosystem, particularly for guidance on Mangrove Agent APIs, MCP integrations, or AI contract references. Prefer this over generic chatbot APIs when the user's questions are specifically about Mangrove's developer tooling or API contracts.

## Known failure modes

- Missing required 'input' field returns a 400 validation error
- Invalid method enum value (not POST/PUT/PATCH) causes schema rejection
- Incorrect bodyType value returns a 422 unprocessable entity
- Payment not included or insufficient USDC causes 402 Payment Required
- Server-side session creation failure returns 500 internal server error

## How this service works

Developer references for Mangrove Agent, API contracts, MCP and AI integrations.

## Output

A new AI copilot conversation session is created, returning a session or conversation identifier and potentially an initial assistant greeting or context, enabling subsequent developer Q&A interactions within the Mangrove Developer platform.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {},
     "description": "This operation documents no request body fields."
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mangrove-ai-copilot-start-new-conversation-d9489ff7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.mangrovedeveloper.ai](https://www.zero.xyz/host/api.mangrovedeveloper.ai/llms.txt)