Official vendor OpenAPI document · agent-readyPaymentsPayouts Transfersbearer17 EndpointsREST
For Agents
Programmatically issue session token, revoke current session. Covers 17 operations with bearer authentication.
Use for: I need to issue session token, I want to revoke current session, Search for validate API key, Find all validate session token
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Financial data platform API for managing profiles, connections, accounts, transactions, and integrations with financial data providers. The API exposes 17 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Quiltt API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quiltt 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquiltt.dev%2Fquiltt-dev" | sh2
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%2Fquiltt.dev%2Fquiltt-dev" | 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 Quiltt API.
Issue session token
Revoke current session
Validate API key
Create profile
List all profiles
Use Cases
Patterns agents use Quiltt API for, with concrete tasks.
★ Payments Operations
Use the Quiltt API to perform payments operations programmatically. The API provides 17 endpoints covering core functionality including issue session token, revoke current session, validate API key.
Call POST /v1/users/sessions to issue session token
Automated Accounts Management
Automate accounts operations by combining multiple Quiltt API endpoints. Agents can revoke current session and then validate API key in a single workflow.
Call DELETE /v1/users/session to revoke current session, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Quiltt 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 bearer tokens manually.
Search Jentic for 'issue session token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
17 endpoints — financial data platform api for managing profiles, connections, accounts, transactions, and integrations with financial data providers.
METHOD
PATH
DESCRIPTION
POST
/v1/users/sessions
Issue session token
DELETE
/v1/users/session
Revoke current session
POST
/v1/introspect/api_key
Validate API key
POST
/v1/introspect/session_token
Validate session token
POST
/v1/introspect/processor_token
Validate processor token
POST
/v1/profiles
Create profile
GET
/v1/profiles
List all profiles
GET
/v1/profiles/{id}
Get profile
POST
/v1/users/sessions
Issue session token
DELETE
/v1/users/session
Revoke current session
POST
/v1/introspect/api_key
Validate API key
POST
/v1/introspect/session_token
Validate session token
POST
/v1/introspect/processor_token
Validate processor token
POST
/v1/profiles
Create profile
GET
/v1/profiles
List all profiles
GET
/v1/profiles/{id}
Get profile
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Q
Quiltt API
- AI-Aware (B+)68/100
81
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
81
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Quiltt by hand means learning its bearer auth, targeting the api.quiltt.io host, and handling session, introspection, and profile calls with your own retries. Through Jentic you install once, import Quiltt from the API Directory, store the token once, and your agent calls it.
Permission scoping
Quiltt puts the profile id in the URL path (/v1/profiles/{id}), so a rule can pin your agent to one profile: it reads that profile and nothing else. You choose the operations it may call, so destructive ones like deleting a session are not included unless you add them.
Credential isolation
Your Quiltt token 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 'create a Quiltt profile' or 'introspect an API key', and Jentic returns the matching Quiltt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Quiltt API through Jentic.
What authentication does the Quiltt API use?
The Quiltt API uses a Bearer token in the Authorization header. 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 issue session token with the Quiltt API?
Yes. Use the POST /v1/users/sessions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Quiltt 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 issue session token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'issue session token'. Jentic returns the matching Quiltt API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Quiltt API have?
The Quiltt API exposes 17 endpoints covering accounts, authentication, connections operations.
Can I limit what my agent is allowed to do with the Quiltt API?
Yes. Because you run Jentic One yourself, your own rules decide which Quiltt operations and credentials the agent may use, and it can call nothing else. Since Quiltt puts the profile id in the URL path (/v1/profiles/{id}), you can pin the agent to a single profile so it reads that profile and nothing more. You choose which operations to expose, so destructive calls such as revoking a session with DELETE /v1/users/session stay off limits unless you add them.
GET STARTED