Skip to content

Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

ForwardFlowAPI explorer

API explorer

Read the request schema and try an engine operation from this page. For natural-language questions, use Connect an AI assistant.

Choose how the request is sent. Without a credential in this viewer, requests use the workspace’s same-origin proxy and its server-held key. To use your party’s access, choose the intended engine in the viewer, select Authorize and enter either an API key or a Bearer credential. Supply one method only; authenticated requests go directly to the selected server.

The viewer does not persist authorization across reloads. Executing an operation uses the engine’s normal capacity and rate allowance. Read the access rules before running a large analysis.

To request your own access token, email info@btcnow.com. BTC Now delivers it privately. In the viewer’s Bearer authorization field, enter the token itself; the viewer adds Bearer to the request header. This differs from an MCP client’s generic header value, where you enter the full Bearer YOUR_ACCESS_TOKEN text. Choose only one authorization method.

The schema comes from the engine serving this workspace. If the explorer cannot load, open the workspace schema or the hosted engine’s schema. Each describes the build serving that address.

Loading the API explorer… If the viewer does not appear, open the schema directly.