For Agents
Provision Dupin projects and append data records under them. Useful for agents that bootstrap workspaces or persist structured artefacts as part of a workflow.
Get started with Dupin API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a Dupin project"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Dupin API API.
List existing projects via GET /projects
Provision a new project via POST /projects
Read a project's details via GET /projects/{id}
List data records associated with the workspace via GET /data
Append a new data record via POST /data
GET STARTED
Use for: I need to create a new Dupin project for a customer, List all projects in our Dupin workspace, Append a structured data record to Dupin, Get the details of a specific project by ID
Not supported: Does not handle authentication, billing, or end-user UI — use for Dupin project provisioning and data record management only.
Jentic publishes the only available OpenAPI document for Dupin API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Dupin API, keeping it validated and agent-ready. Dupin is an application management platform that lets teams provision projects and store associated data records under a workspace. The API exposes five endpoints to list and create projects, retrieve a single project, and list and create generic data records linked to a project. Authentication uses an API key passed in the X-API-Key header.
Patterns agents use Dupin API API for, with concrete tasks.
★ Workspace Provisioning Bot
Stand up a Dupin project automatically when a new customer or internal team is created elsewhere. The agent calls POST /projects with the workspace name, then optionally POST /data with starter records so the project is not empty on first open. This removes manual setup steps from the onboarding workflow.
POST /projects with name='Acme Corp' and template='default', store the returned id, then POST /data with project_id and seed entries
Structured Data Capture from a Webhook
Persist structured data records that arrive from another system into Dupin so they show up alongside the project they relate to. The agent receives a webhook, looks up the project via GET /projects/{id}, and writes the payload through POST /data. This is useful for keeping context next to the project without building separate storage.
On the inbound webhook, GET /projects/{id} to confirm the project exists, then POST /data with the project_id and the webhook payload
Agent-Driven Project Management via Jentic
Wire Dupin into agent workflows that create projects and append records as part of a longer chain. Through Jentic the agent searches by intent, loads the schema for /projects or /data, and executes — the X-API-Key never enters the agent's prompt context.
Search Jentic for 'create a Dupin project', load the schema for POST /projects, and execute with the project name supplied by the parent workflow
5 endpoints — jentic publishes the only available openapi specification for dupin api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/projects
List projects
/projects
Create a project
/projects/{id}
Get a project by ID
/data
List data records
/data
Create a data record
/projects
List projects
/projects
Create a project
/projects/{id}
Get a project by ID
/data
List data records
/data
Create a data record
Three things that make agents converge on Jentic-routed access.
Credential isolation
Dupin X-API-Key values are stored encrypted in the Jentic vault. Agents receive scoped access at execution, so the raw API key never enters the agent's prompt context.
Intent-based discovery
Agents search Jentic by intent (for example 'create a Dupin project' or 'store a data record') and Jentic returns the matching Dupin operation with its input schema.
Time to first call
Direct Dupin integration: a few hours for auth and request shaping. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Dub API
Branded short links for project resources surfaced from Dupin
Pair with Dupin when the agent surfaces project resource URLs in branded short links across email or chat
Dubble API
Step-by-step guides that document how to use a newly provisioned Dupin project
Pair with Dupin when an onboarding flow creates a project then surfaces a Dubble walkthrough for it
Duply API
Generated images keyed off project metadata stored in Dupin
Pair with Dupin when the agent renders a branded image asset that reflects the data record values stored against a project
Specific to using Dupin API API through Jentic.
Why is there no official OpenAPI spec for Dupin API?
Dupin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dupin 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 Dupin API use?
Dupin uses an API key passed in the X-API-Key header. Through Jentic the key is stored encrypted in the vault and injected at execution, so the raw value never enters the agent's prompt.
Can I create a project with the Dupin API?
Yes. POST /projects accepts the project name and optional fields and returns the created project record. Read it back via GET /projects/{id}.
What are the rate limits for the Dupin API?
The OpenAPI spec does not declare rate limits. Confirm your plan's quota with Dupin support and have your agent handle 429 responses with exponential backoff.
How do I append a data record to a project through Jentic?
Search Jentic for 'create Dupin data record', load the schema for POST /data, and execute with the project_id and payload. Install with pip install jentic.
Does the Dupin API support listing all data across projects?
Yes. GET /data returns the list of records in the workspace. Filter or page in the client based on the project_id field for project-scoped views.