Agiled App Agiled API
★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey47 EndpointsREST
For Agents
Drive a small-business management platform: create invoices, manage CRM contacts and deals, schedule meetings, and attach activities to records.
Use for: Create a new invoice for a client and email a payment reminder, List all open deals in the proposal stage of my pipeline, Add a contact to my CRM and link them to an existing account, Schedule a discovery meeting with a contact and create a related event
Not supported: Does not handle payment processing, payroll, or product manufacturing — use for CRM, invoicing, scheduling, and lightweight project tracking inside Agiled only.
Jentic publishes the only available OpenAPI specification for Agiled API, keeping it validated and agent-ready. Agiled is an all-in-one business management platform combining CRM, invoicing, scheduling, project management, and document handling. The 1.0.0 spec exposes 47 endpoints across invoices, accounts, contacts, deals, meetings, events, notes, files, activities, and pipelines. Every endpoint authenticates with an api_token query parameter, making it straightforward to embed in serverless functions or no-code workflows.
Install Jentic One Beta
Connect the Agiled API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agiled 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Agiled API.
Create and send invoices with line items and reminders via /invoices and /invoices/{id} endpoints
Manage CRM accounts, contacts, and deals through full CRUD endpoints under /accounts, /contacts, /deals
Schedule meetings and event types via /meetings, /events, and /event-types
Attach notes, files, and activities to deals or contacts via /notes, /files, /activities
Search across account data with a single POST /search call
Move deals through pipeline stages tracked by /pipeline endpoints
Use Cases
Patterns agents use Agiled API for, with concrete tasks.
★ Invoicing and Payment Reminders
Generate invoices from completed projects or recurring engagements and trigger reminders against unpaid invoices. The agent calls POST /invoices to create the document and PUT /invoices/{id} to dispatch a reminder. Suitable for freelancers and small agencies running their billing through Agiled.
POST /invoices with the line items for project 42, then PUT /invoices/{id} to send a reminder if status is unpaid after 14 days
CRM and Pipeline Management
Maintain a clean book of business by syncing leads from web forms or marketing tools into Agiled accounts and deals. The agent uses POST /accounts and POST /contacts to create records, then POST /deals to attach an opportunity in the right pipeline stage. Useful for solo operators and small teams that consolidate CRM with billing in one platform.
On a new lead form submission, POST /accounts, POST /contacts linked to that account, then POST /deals at stage 'New'
Scheduling and Activity Logging
Coordinate discovery calls and project meetings via POST /meetings while logging activities and notes against the linked deal. The agent ties the meeting outcome back to /activities and /notes so the deal record stays current. Suited for sales-led service businesses where every call should leave a paper trail.
POST /meetings for a 30-minute slot tomorrow with contact 88, then POST /activities with type='call' linked to deal 12
Agent-Driven Back-Office Automation
Run a Jentic-connected agent that watches inbox events or webhook triggers and writes the appropriate Agiled records — invoice, deal, contact, or note — without human routing. The agent searches Jentic for each operation, loads schemas, and chains calls. This replaces hand-coded back-office scripts for solo operators.
When a new contract is signed, create the contact, create the deal at 'Won', generate the first invoice, and post a note linking the artefacts
Key Endpoints
47 endpoints — jentic publishes the only available openapi specification for agiled api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/invoices
Create a new invoice
PUT
/invoices/{id}
Send a payment reminder for an invoice
POST
/accounts
Create a CRM account
POST
/contacts
Create a contact
POST
/deals
Create a deal
POST
/meetings
Schedule a meeting
POST
/search
Search across account data
POST
/invoices
Create a new invoice
PUT
/invoices/{id}
Send a payment reminder for an invoice
POST
/accounts
Create a CRM account
POST
/contacts
Create a contact
POST
/deals
Create a deal
POST
/meetings
Schedule a meeting
POST
/search
Search across account data
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Agiled api_token credentials are stored in the Jentic vault and appended as the api_token query parameter at execution time. Agents never see the raw token.
Intent-based discovery
Agents search by intent (e.g. 'create an invoice' or 'add a CRM contact') and Jentic returns the matching Agiled operation with its input schema and tag-grouped resource.
Time to first call
Direct Agiled integration: half a day for query-string auth, pagination quirks, and reminder routing. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Payment processing layer for invoices generated in Agiled
Use Stripe when an Agiled invoice needs a payment link or recurring subscription that Agiled itself does not handle.
FAQs
Specific to using Agiled API through Jentic.
Why is there no official OpenAPI spec for Agiled API?
Agiled does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agiled API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Agiled API use?
Agiled uses an api_token passed as a query parameter on every request (apiTokenQuery scheme). Through Jentic the token sits in the credential vault and is appended at execution; agents never see the raw value.
Can I create an invoice and send a reminder with the Agiled API?
Yes. POST /invoices to create the invoice with its line items, then PUT /invoices/{id} (the reminder route) to dispatch a payment reminder to the client. The two calls are separate so reminders can run on a schedule.
What are the rate limits for the Agiled API?
Agiled does not publish a documented per-second rate limit. The platform throttles abusive bursts at the network layer; agents should retry-with-backoff on 429 responses and serialise high-volume operations across accounts and contacts.
How do I create a deal and attach a contact through Jentic?
Use the Jentic search 'create an agiled deal'. Jentic returns POST /deals; load its schema, supply contact_id and account_id, and execute. The deal is created at the default pipeline stage and linked to the contact in the same call.
Does Agiled expose a global search across CRM data?
Yes. POST /search accepts a search term and returns matching accounts, contacts, deals, and invoices in one response, which is useful when an agent only has a partial reference and needs to disambiguate before acting.
GET STARTED