--- title: Claude API Integration on Truto slug: claude category: Conversational Intelligence canonical: "https://truto.one/integrations/detail/claude/" --- # Claude API Integration on Truto **Category:** Conversational Intelligence **Status:** Beta ## Unified APIs ### Unified Usage Metering API - **Products** — Products represent the services or products that are being used by the organization for a particular integration. - **Usage** — Per-period usage record. Grain is (product, period) by default and (user, product, period) for AI tools and per-user-pivoted vendors. All metric sub-objects are optional; emitters populate only what they know. - **Users** — Members / seats inside the source application (team, workspace, organization). ## How it works 1. **Link your customer's Claude account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Claude.** The Proxy API is a 1-to-1 mapping of the Claude API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Offer native AI features powered by your users' own Claude accounts** — Let your customers connect their own Anthropic API keys so AI features run on their billing, quota, and compliance posture. This avoids you fronting LLM costs while still delivering deeply embedded AI capabilities. - **Meter and bill AI usage as a product line** — Use Truto's Unified Usage Metering API to track input, output, and cached tokens per end-user, then convert that into AI credits, seat-based pricing, or pass-through billing. This makes AI feature profitability measurable from day one. - **Enable BYO-model deployments for regulated customers** — LegalTech, FinTech, and Healthcare buyers often mandate that LLM calls go through their own Anthropic contract for data residency and audit reasons. Offering a Claude connect flow unlocks deals where a shared backend model is a procurement blocker. - **Power agentic and document workflows inside your product** — Embed Claude to drive contract review, ticket triage, meeting intelligence, or structured extraction over long documents. Customers get a 200K-context reasoning engine wired into your existing UI instead of switching to a separate AI tool. - **Track per-tenant AI consumption for governance** — Surface usage analytics so admins inside your customer's org can see which teams, workspaces, or features are consuming the most tokens. This is increasingly a requirement for enterprise IT and FinOps buyers. ## What you can build - **Per-tenant Claude connect flow** — Let each customer link their own Anthropic account via Truto so all AI calls in your product run against their key, models, and quotas. - **AI credits and usage-based billing** — Pull token usage (input, output, cached) per user from the Unified Usage Metering API and convert it into credits, overages, or invoiced line items. - **Per-feature token attribution dashboard** — Tag Claude calls by feature (summarization, extraction, agent) and report consumption back to your customer's admins for FinOps and chargeback. - **Model selection controls for admins** — Expose Haiku, Sonnet, and Opus as configurable tiers inside your product so customers can route cheap tasks to Haiku and complex reasoning to Opus. - **Long-document analysis features** — Ship contract review, RFP analysis, or 10-K extraction features that lean on Claude's 200K context window without forcing you to build chunking infrastructure. - **Structured extraction via Tool Use** — Build features that return guaranteed JSON — meeting summaries, ticket classifications, invoice fields — using Claude's forced tool_choice for reliable downstream automation. ## FAQs ### How do end-users authenticate their Claude account? Anthropic's API uses API key authentication. Through Truto, your end-users paste their Anthropic API key into a connect flow, and Truto securely stores and rotates the credential on their behalf so your backend never handles raw keys. ### Does Truto have prebuilt tools for Claude today? No prebuilt tools for Claude are shipped yet — they are built on request. If you need specific operations against the Messages API or other Anthropic endpoints, Truto can scope and deliver them as part of onboarding. ### Can I meter token usage per end-user for billing? Yes. Truto's Unified Usage Metering API normalizes Products, Usage, and Users across LLM providers, so you can attribute input, output, and cached tokens to specific tenants and turn that into credits or invoices. ### Which Claude models are supported? Any model available on your end-user's Anthropic account — including the Haiku, Sonnet, and Opus tiers — can be targeted, since calls are made against their authenticated key and Anthropic's published model identifiers. ### How are rate limits handled? Anthropic enforces per-organization rate limits tied to the API key in use. Because each tenant connects their own key, limits scale with your customer's Anthropic plan rather than a shared pool you have to manage. ### Does this support long-context and multimodal requests? Yes. Claude's Messages API natively supports 200K+ token contexts and image inputs, so document-heavy and vision workflows work without additional chunking or preprocessing on your side. ## Related reading - [Connect Boomi to Claude: Manage Permissions & Governance via MCP](https://truto.one/blog/connect-boomi-to-claude-manage-user-permissions-and-governance/) — Learn how to connect Boomi to Claude using a managed MCP server. Automate user permissions, roles, and access reviews without building custom API integrations. - [Connect Canny to Claude: Automate Feedback & Roadmaps via MCP](https://truto.one/blog/connect-canny-to-claude-analyze-roadmaps-user-engagement/) — Learn how to build and configure a Canny MCP server to connect Claude directly to your product roadmap. Automate feedback triage, voting, and feature requests. - [Connect Cal.com to Claude: Automate Scheduling Workflows](https://truto.one/blog/connect-calcom-to-claude-automate-scheduling-workflows/) — Learn how to connect Cal.com to Claude using a managed MCP server. Automate bookings, schedules, and team availability without writing integration code. - [Connect Billsby to Claude: Automate Invoices & Subscriptions via MCP](https://truto.one/blog/connect-billsby-to-claude-manage-invoices-payment-reattempts/) — Learn how to connect Billsby to Claude using a managed MCP server. Execute complex billing workflows, refund invoices, and manage subscriptions via chat. - [Connect Basecamp to Claude: Sync Documentation & Project Schedules via MCP](https://truto.one/blog/connect-basecamp-to-claude-sync-documentation-project-schedules/) — Learn how to connect Basecamp to Claude using a managed MCP server. Automate task delegation, sync project schedules, and manage team communication. - [Connect BigCommerce to Claude: Automate Support & Order Fulfillment](https://truto.one/blog/connect-bigcommerce-to-claude-automate-support-order-fulfillment/) — Learn how to connect BigCommerce to Claude using a managed MCP server. Automate order tracking, catalog management, and customer support workflows.