Connect an agent

One MCP server with 24 tools. Streamable HTTP, stateless, JSON responses. Every tool lists its price in its description, so an agent can decide before it calls.

Bond marine chronometer, ca. 1812
Bond marine chronometerca. 1812
Add the serverOne line01
The agent reads the toolsSchema, example, price02
Pay per call100 free calls a day03

Claude Code

claude mcp add --transport http tausendwerk https://api.tausendwerk.xyz/mcp

With a key: claude mcp add --transport http tausendwerk https://api.tausendwerk.xyz/mcp --header "Authorization: Bearer tw_live_…"

Claude Desktop, Cursor and other clients

Add a remote MCP server with this URL: https://api.tausendwerk.xyz/mcp. In clients that use a JSON file:

{
  "mcpServers": {
    "tausendwerk": {
      "type": "http",
      "url": "https://api.tausendwerk.xyz/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_…"
      }
    }
  }
}

Leave out headers to use the free allowance.

REST

Every tool is also POST https://api.tausendwerk.xyz/v1/{tool} with a JSON body. GET https://api.tausendwerk.xyz/v1/tools lists all tools with their schemas. The OpenAPI document and llms.txt describe the same.

Payment

Free: 100 calls per day per client, no key.

Prepaid credit: buy CHF 5, 20, 50, 200 at api.tausendwerk.xyz/billing and get an API key. Each successful call takes its price from your credit. Credit does not expire.

Over the limit: the API answers 402 Payment Required with the price and a top-up link, so an agent can ask its owner.

Apify: the same tools run as an Apify Actor, billed per call by Apify in USD. Useful if your agent already pays through Apify.

Errors: invalid input returns 400 with the schema errors. You are not charged for it.

Good to know

  • Results are computed, not generated. The same input gives the same output.
  • Content you send is processed in memory and not stored. See privacy.
  • The two language-level tools call a language model; all others are plain code.