launchtandem.com valid

Tandem

Tandem is the full production stack — custom domains, managed Postgres & MySQL, object storage, Stripe payments, email, DNS + TLS, and Git deploys — in one place, built for humans and AI agents as equals. Agents are first-class: an agent can create and run its own organization, provision real infrastructure, and ship to production over a typed REST API and an MCP server. Use as much or as little as you want, keep your existing services, and leave with everything — zero vendor lock-in.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T19:54:38.406Z. Cached copy · Source on launchtandem.com

# Tandem

> Tandem is the full production stack — custom domains, managed Postgres & MySQL, object storage, Stripe payments, email, DNS + TLS, and Git deploys — in one place, built for humans and AI agents as equals. Agents are first-class: an agent can create and run its own organization, provision real infrastructure, and ship to production over a typed REST API and an MCP server. Use as much or as little as you want, keep your existing services, and leave with everything — zero vendor lock-in.

Humans drive a visual cockpit; agents drive a typed API and MCP. Same system underneath. An agent can onboard itself from scratch over plain HTTP — no human pre-setup required.

## For AI agents: start here

You can create a Tandem organization from scratch, get an agent token, and connect your MCP tools — in a single anonymous call. No human setup needed first.

- MCP endpoint: `https://portal.launchtandem.com/mcp` (Streamable HTTP, JSON-RPC over HTTP POST)
- Token format: `tdm_` + 48 hex characters (treat it like a password)

Bootstrap — one anonymous call creates the org, emails the human owner a claim link, and returns YOUR agent token (the `token` field only appears for anonymous callers):

```bash
curl -s https://portal.launchtandem.com/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"create_account_and_claim_link","arguments":{"ownerEmail":"you@example.com","organizationName":"Acme Inc."}}}'
```

The response's `result.content[0].text` is a JSON string containing `token`, `claimUrl`, and a ready-to-run `setupHint`. Persist the token in your MCP client — e.g. Claude Code:

```bash
claude mcp add --scope user --transport http tandem \
  https://portal.launchtandem.com/mcp \
  --header "Authorization: Bearer tdm_…"
```

Then call `tools/list` to see everything you can provision (databases, storage, domains, deploys, payments, email, secrets…). The human owner uses `claimUrl` to take ownership and add billing; you can start building the moment step 1 returns.

Full guide: https://docs.launchtandem.com/bootstrapping

## Docs

- [Bootstrapping an account](https://docs.launchtandem.com/bootstrapping): self-onboard a fresh agent over HTTP, get a token, wire up MCP.
- [Connecting agents](https://docs.launchtandem.com/connecting-agents): point Claude, Claude Code, OpenAI/Codex, Cursor, and other MCP clients at Tandem's MCP server.
- [Documentation](https://docs.launchtandem.com): all guides, including connecting a repo, custom domains and DNS.

## Sign up

- [Sign up as an agent](https://portal.launchtandem.com/signup?as=agent): machine-native onboarding (or just run the bootstrap call above).
- [Sign up as a human](https://portal.launchtandem.com/signup): the visual cockpit.

## What Tandem provisions

Custom domains · managed Postgres & MySQL · object storage · Stripe payments · email mailboxes · DNS + TLS · deploy from Git · secrets & env · agent API tokens. Bring your own services and c
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=launchtandem.com · GET /v1/domain/launchtandem.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for launchtandem.com:
1. POST https://agentwebmap.com/v1/sites/launchtandem.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://launchtandem.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/launchtandem.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/launchtandem.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.