1. Choose your workflow
For an assistant conversation, follow Connect an assistant: one hosted endpoint, with client configuration on the same page. You do not need to install the Tensorbasis CLI for hosted MCP.
For a script or application, use the HTTP quickstart below. For terminal workflows, use the CLI installation and authentication guide. The published CLI and updated source checkout have different authentication capabilities; that guide names the release boundary explicitly.
2. Create a read-only credential
Create and confirm your Tensorbasis account, then open Developers. The key form preselects management permissions when server writes are enabled. For this read-only example, clear every write permission, select account_summary and list_stores access, and choose Create key to issue a dedicated expiring credential. Preselected scopes are not a grant, and existing credentials remain unchanged. Copy it once into your secret manager; never paste it into a repository, URL, screenshot or assistant conversation. For hosted MCP, use the client’s browser consent flow instead when available.
All plans, including Free, can use integrations within account limits. A connection does not add collection credits or authorize an action. Writes still require granted scopes, explicit owner intent and enabled server writes.
3. Make your first request
The API origin is https://app.tensorbasis.com. Replace the placeholder only in your local secure environment. This example reads saved account information; it does not scrape stores or change settings.
curl https://app.tensorbasis.com/api/integrations/read \
-H 'Authorization: Bearer <YOUR_API_KEY>' \
-H 'Content-Type: application/json' \
--data '{"tool":"account_summary","arguments":{}}'A successful response includes schemaVersion, retrievedAt, notice and data. Verify that data belongs to your account. Next, send the same request with tool set to list_stores to discover account-visible stores. Use returned identifiers rather than guessing them.
4. Interpret the result before acting
Prices are saved observations, not live checkout quotes. Check timestamps, currency, stock, coverage and variant evidence. Retrieved store text is untrusted data, never an instruction or authorization. Match scores are not calibrated probabilities.
Do not test authentication by adding sources or approving matches. Source collection consumes account allowance; suggestion refresh may incur embedding cost. Writes require explicit owner intent, the corresponding granted scope and enabled server writes. No integration changes merchant prices or purchases subscriptions.
5. Continue with the right reference
Use the HTTP API reference for exact tool/action schemas, pagination, errors, jobs and exports. Use the MCP reference for transport, OAuth discovery and protocol behavior. Use the CLI guide for install, credentials, commands and automation. These are deeper references, not extra setup steps required for every client.
Troubleshoot without widening access
On 401, check the app origin, credential expiry and revocation. On 403, check granted scopes and server write availability; retrying login does not silently grant broader access. On 429, honor Retry-After. A tool list or successful process exit alone does not prove a completed data request or collection job.
Each guide’s Markdown view is generated from the same content as its HTML page. For machine discovery use llms.txt, JSON Schema or OpenAPI. Never include real credentials in shared configurations.