---
title: "Tanso access and deployment"
canonical: https://tansohq.com/auth.md
description: "Read Tanso product information and pricing, contact Tanso with permission, and integrate a tanso-oss instance using scoped credentials."
---

> Full site context for agents: https://tansohq.com/llms.txt

# Tanso access and deployment

This guide covers the public Tanso monetization website and integration with an operated tanso-oss instance.

## Read public information

No account is required to read this website. Use explicit .md links or Accept: text/markdown. JSON information is at https://tansohq.com/api/agent. Tanso's own hosting prices are at https://tansohq.com/pricing.json.

Self-hosted software is free under AGPL-3.0. Paid hosting starts at $375/month and requires contact. There is no free hosted Tanso tier. [Full pricing](https://tansohq.com/pricing.md).

## Contact Tanso with permission

Email kat@tansohq.com for paid hosting. The existing contact endpoint also accepts inquiries: POST https://tansohq.com/api/evaluation-request. Required JSON fields are requestId (UUID) and email (valid email). Optional fields are productUrl (http or https website, or a plain domain), task (up to 2,000 characters), and source (up to 80 letters, digits, underscores, or hyphens).

Submit a contact request only with the person's permission. This does not create an account, start hosting, subscribe to a paid plan or authorize a purchase.

Success is HTTP 200 with {"success":true,"requestId":"..."}. Treat the request as received only after that response. Retry a timeout with the same requestId and identical payload. HTTP 400 means invalid input; 405 means unsupported method; 5xx means delivery was not confirmed. Email fallback: kat@tansohq.com.

## Integrate an instance

Obtain the instance URL and scoped credentials from its operator. Follow the [deployment docs](https://tanso.mintlify.app) and [repository instructions](https://github.com/tansohq/tanso-oss). Never send instance credentials to tansohq.com.

## Customer signup and purchases

An operator may enable a public catalog per account. GET {instance}/public/v1/catalog/{slug}/pricing.json reads that operator's product pricing. POST {instance}/public/v1/catalog/{slug}/signup creates a customer on the operator's free plan and returns a customer-scoped API key (ck_...) with read and purchase scopes. The provisional customer is claimed through a completed Stripe payment. The instance serves its signup runbook at {instance}/agent-signup.md and lists it at {instance}/.well-known/agent-skills/index.json.

These are the operator's customer flows, not Tanso's paid-hosting signup. The marketing domain does not expose a billing API, purchase endpoint or MCP server.

The optional MCP server is enabled and configured by the operator. Review the current docs and scoped permissions. Money-moving tools require explicit confirmAction. Confirm the intended task and permitted spending, then verify the resulting state.

- [Product overview](https://tansohq.com/product/agent-monetization.md)
- [MCP configuration](https://tanso.mintlify.app/mcp.md)
- [Quickstart](https://tanso.mintlify.app/quickstart)
- [Site index](https://tansohq.com/llms.txt)