# MCP _{The product surface is marked} _{**Coming soon**} _{while the catalog and pricing story settle. Treat in app tables as} _{**menu plus price hint**}_{, not a final contract, until billing ships beside the SDK story your team configures.}

_{This page means}

This page is	This page is not
_{Operator habits for agents calling ARIA}	_{A full MCP spec tutorial for every client}
_{Read versus write as a safety lens}	_{A guarantee that every tool name will never change}

_{Tool catalog (how to read it)}

_{**Read tools**} _{inspect ideas, facets, validation status, exports. They should be your default.} _{**Write tools**} _{enqueue work or change state (for example validation start, build launch style operations). Teach your team to treat them like} _{**admin buttons**}_{: explicit intent, then poll job ids, no fire and forget mutations.} _{List rates in the UI start around} _{**one cent per successful call**} _{on many discover reads, with higher hints on heavier writes.} _{**Bundle discounts**} _{and enterprise agreements are part of the product story. Confirm numbers in billing when live.}

_{Habits for Agent Builders}

{% stepper %} {% step %} _{**Bootstrap context first**} _{Snapshot or targeted reads so the model knows what is validated, what is live, and which guardrails apply.} {% endstep %} {% step %} _{**Plan with tools, not guesses**} _{Use read tools before any write. Writes return job ids you can poll.} {% endstep %} {% step %} _{**Stream progress back to humans**} _Poll _`*.status` _{tools or subscribe where your tier supports streaming so the UI shows live pipeline state while the model narrates what changed..} {% endstep %} {% endstepper %} ***

_{Ask a question (checkpoint)}

_{If this agent ran unattended for an hour, what is the maximum dollar and state change you accept?}
_{If you cannot answer, tighten scopes and caps before you widen access.}

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ariaagi.com/platform/mcp.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.