Give software and AI a governed path to enterprise work.
Use C1.ai through the REST API, generated SDKs, Terraform, connectors, webhooks, or MCP. Each interface starts from an identity, a tenant, and the permissions granted to that caller.
Choose the interface that matches the job.
REST API
Query C1.ai data and automate supported operations against your tenant. Start with the API guide, then use the OpenAPI contract for the exact paths, parameters, and response schemas.
Generated SDKs
Work with the C1.ai API from Go, Java, JavaScript, Python, or Ruby using generated clients that follow the published API contract.
Terraform
Manage supported C1.ai resources as code with the C1 Terraform provider. Use the provider guide for authentication and resource coverage.
Connectors
Bring application accounts and resources into C1.ai. Configure an existing connector, build against a REST API with baton-http, or use the connector SDK for a custom integration.
Webhooks
Send C1.ai events to external systems and return decisions through documented inbound and outbound webhook flows.
MCP
Connect authorized AI clients to a C1.ai tenant, or use the separate public documentation MCP server to search C1.ai product and developer documentation.
Two MCP surfaces. Different trust boundaries.
Tenant MCP connects an authorized user to one C1.ai tenant. The tenant host, permissions, and available tools come from that tenant.
Documentation MCP is public and read-only. It searches published C1.ai documentation and cannot reach customer data or tenant configuration.
Start from the contract, not a copied example.
Resolve the tenant first
C1.ai API hosts and tenant MCP hosts are tenant-specific. Use the host provided by your C1.ai tenant; do not substitute www.c1.ai.
Pick the right identity
Use a personal API credential for a person. Use a service principal and OAuth 2.0 client credentials for a service or workload.
Scope before you ship
Limit the caller to the role and permissions the integration needs. The API guide and service-principal docs describe the available credential paths.
Read the live schema
The root OpenAPI URL is the machine-readable REST contract. Generated SDKs and reference documentation derive from that contract.
Handle real failures
Treat authentication, authorization, validation, rate-limit, and server responses as distinct outcomes. Preserve the response body and request context when you retry or escalate.
Keep tenant data in tenant surfaces
The public docs MCP answers documentation questions only. Send tenant requests through an authorized C1.ai API or tenant MCP connection.
Live entry points for agents and developers.
OpenAPI
The canonical machine-readable contract for the C1.ai REST API.
AI catalog
Root discovery metadata for the C1.ai public agent-facing surfaces.
llms.txt
A concise map of C1.ai, its interfaces, and the canonical pages to retrieve.
Documentation MCP
The public, read-only MCP endpoint for C1.ai documentation.