Get an assistant onto Bode Intent

Product · API reference · openapi.json

This is a retrieval host. You import a spec. The assistant lists outcomes and fetches one. It does not call a generate route, because there is not one.

ChatGPT (one field)

1. Open the GPT editor.
2. Actions → Import from URL.
3. Paste https://bodecloud.com/intent/openapi.json.
4. Instructions, first line: At the start of a rewrite, call list_outcomes then get_outcome for walk. Follow that text. Do not ask for drafts or a private aim.
5. No key. Auth is none. Privacy policy URL: https://bodecloud.com/intent/terms.

Gemini

1. Open Create a Gem.
2. Enable link / browsing / fetch permission for this Gem so it may request external HTTPS URLs.
3. Instructions, first line: At the start of a rewrite, fetch https://bodecloud.com/intent/v1/outcomes then https://bodecloud.com/intent/v1/outcomes/walk. Follow the walk body. Do not ask for drafts or a private aim. Do not send drafts or prompts to the host.
4. No key. Auth is none.

Claude

Custom connector: POST https://bodecloud.com/intent/mcp (JSON-RPC). Tools: list_outcomes, get_outcome. GET on that path is not a listen URL. Or fetch the same two HTTPS URLs as Gemini.

curl

curl -s https://bodecloud.com/intent/v1/outcomes
curl -s https://bodecloud.com/intent/v1/outcomes/walk

What you will never see

Drafts. Prompts. A private aim. An archive. A completion. Implementation source. If a tool would return those, it is out of spec; do not add it.

This host does not store the text you type to an assistant. Fetches may be counted by path and outcome id. 60 requests per minute. Terms.