canonical: https://jentic.com/apis/tilled.com/tilled

# Tilled API

The Tilled API is organized around [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer). Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. You can use the Tilled API in test mode, which does not affect your live data or interact with the banking netwo. The API exposes 114 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically get an account, update an account. Covers 114 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Get an Account
- Update an Account
- Add an Account Capability
- Delete an Account Capability
- Create a Connected Account
- List all Connected Accounts

## Use cases

### AI and Machine Learning Operations

Use the Tilled API to perform ai ml operations programmatically. The API provides 114 endpoints covering core functionality including get an account, update an account, add an account capability.

Example prompt: Call GET `/v1/accounts` to get an account

### Automated Users Management

Automate users operations by combining multiple Tilled API endpoints. Agents can update an account and then add an account capability in a single workflow.

Example prompt: Call PATCH `/v1/accounts` to update an account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tilled API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'get an account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/accounts` | Get an Account |
| PATCH | `/v1/accounts` | Update an Account |
| POST | `/v1/accounts/capabilities` | Add an Account Capability |
| POST | `/v1/accounts/capabilities/{id}` | Update an Account Capability |
| DELETE | `/v1/accounts/capabilities/{id}` | Delete an Account Capability |
| POST | `/v1/accounts/connected` | Create a Connected Account |
| GET | `/v1/accounts/connected` | List all Connected Accounts |
| DELETE | `/v1/accounts/connected` | Delete a Connected Account |

## Key resources

- **Users** — Users can log into the Tilled Dashboard and authenticate for various requests.
- **Accounts** — An Account can represent a merchant or partner. You can retrieve and manage Account properties such
- **Subscriptions** — Subscriptions allow you to charge a customer on a recurring basis.
- **PaymentIntents** — A Payment Intent is initiated server side to begin the transaction process. The Payment Intent shoul
- **PaymentMethods** — Payment Methods are associated with a Customer and used to satisfy Payment Intents.

## Why Jentic

- **Setup:** Wiring the Tilled API by hand means choosing between its tilled-api-key header and a bearer JWT from the login resource, picking the production or sandbox host, and building the account and capability calls yourself. Through Jentic you install once, import the Tilled API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Tilled puts the capability id in the URL path (`/v1/accounts/capabilities/{id}`), so a rule can pin your agent to one capability: it can create or read that capability and nothing else. You choose the operations it may call, so destructive ones like deleting a capability or a connected account are not included unless you add them.
- **Credential handling:** Your Tilled credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an account' or 'add an account capability', and Jentic returns the matching Tilled API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Tilled API use?

The Tilled API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get an account with the Tilled API?

Yes. Use the GET `/v1/accounts` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tilled API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get an account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get an account'. Jentic returns the matching Tilled API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tilled API have?

The Tilled API exposes 114 endpoints covering users, accounts, subscriptions operations.

### Can I limit what my agent is allowed to do with the Tilled API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Tilled operations and credentials the agent may use. Because Tilled puts the capability id in the URL path (`/v1/accounts/capabilities/{id}`), you can pin the agent to a single capability, letting it create or read that one and nothing else. You choose exactly which operations it may call, so destructive actions like deleting a capability or a connected account stay out of reach unless you explicitly add them.