Skip to main content
The web app is a client of a public HTTP API, and everything it does can be done with curl. The full spec is docs/openapi.json (OpenAPI 3.1, 63 operations): open it in Swagger Editor or any OpenAPI viewer to read every route and try it against the hosted API. Every server-sent event type is described in docs/api-contract.md §3.
  • Base URL: https://api.hellonear.xyz (NEAR testnet), or http://localhost:4000.
  • Auth: a session cookie, hn_session. Get one with POST /v1/auth/demo (guest, no wallet) or with a NEAR wallet: POST /v1/auth/challenge, sign the message (NEP-413), then POST /v1/auth/login. curl works as is (no Origin header); a browser page on another site gets 403 for any call that changes something (CSRF protection).
  • Streams: chat, approve/decline, workflow runs and attack runs answer text/event-stream: run.started, text.delta, tool.called, tool.result, tool.approval_required, run.finished, run.verified and more.
  • Guests get 403 demo_not_allowed for owner actions (wallet policy, freeze, memory edits, rules, schedules); everything else works.
  • Checked live: the last column marks the endpoints called against the hosted API with a guest session on 12 Nov 2026 and answered as documented (owner-only and money-moving endpoints are covered by the backend’s integration tests instead).
System Auth Catalog Minds Chat Runs Approvals Verification Wallet Memory Email Autopilot Connections Telegram Secrets Attack playground