Tilled API

Name: Tilled API
Brand: Tilled API
Availability: InStock

✓ Official Vendor SpecAI/MLLanguage ModelsapiKey, bearer114 EndpointsREST

For Agents

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

Use for: I need to an account, I want to an account, Search for add an account capability, Find all an account capability

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

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.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Tilled API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tilled API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftilled.com%2Ftilled" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftilled.com%2Ftilled" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Tilled API.

Get an Account

Update an Account

Add an Account Capability

Delete an Account Capability

Create a Connected Account

GET STARTED

Start building with Tilled API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Tilled API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

114 endpoints — the tilled api is organized around [rest](http://en.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Tilled API through Jentic.

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.

Tilled API

Connect the Tilled API to your agent

Capabilities

Start building with Tilled API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs