Hoist AIAssets Sign in
Home›Docs›MCP›curl / direct HTTP

curl / direct HTTP.

The planned REST/curl flow for Hoist Assets. It ships at S2-gate alongside the partner intermediary. Today the live HTTP surface is the MCP JSON-RPC endpoint at mcp.assets.hoistai.com/mcp — use any of the seven MCP host install guides to reach it.

REST API — no MCP host requiredRoadmap (S2-gate)
This page is a roadmap document. The REST API at api.assets.hoistai.com and the API-key dashboard at dashboard.assets.hoistai.com/keys ship at S2-gate alongside the partner intermediary. The shapes below are stable enough to integrate against — fields will not be renamed before S2-gate. For a live integration today, use the MCP JSON-RPC endpoint at mcp.assets.hoistai.com/mcp with OAuth 2.1 + PKCE via any of the seven MCP host install guides (Claude Desktop, Claude.ai, ChatGPT, Cursor, Cline, Codex CLI, Gemini CLI).

The config Roadmap (S2-gate)

# Run a PPSR organisation search (planned shape — not callable today)
curl https://api.assets.hoistai.com/v1/ppsr/search \
  -H "Authorization: Bearer $HOIST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"acn":"123 456 789","sandbox":true}'

Steps Roadmap (S2-gate)

  1. Grab an API key from dashboard → keys. The dashboard route lands at S2-gate. Test keys will be free and unlimited against fixtures.
  2. Export: export HOIST_KEY=hoist_test_01HX...
  3. Run the curl above. Response will be JSON; the record PDF URL will be in the response body.

Smoke test Roadmap (S2-gate)

Once S2-gate ships, replace 123 456 789 with any of the fixture ACNs from /sandbox to see different response shapes. Today, exercise the same fixture ACNs through any MCP host using the ppsr_search_org tool against mcp.assets.hoistai.com/mcp.

Troubleshooting

  • OAuth window doesn't open. Check your default browser is set and pop-ups aren't blocked. On macOS you may need to grant curl / direct HTTP accessibility permissions.
  • Tools don't appear after install. Restart the host completely. Some hosts cache the tool list at startup.
  • 403 on calls. Re-approve OAuth — the cached token may have expired or had scopes revoked.
  • Still stuck? Drop a note on GitHub Issues with the host name and the error message.

Other hosts