Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbasic, oauth289 EndpointsREST
For Agents
Programmatically retrieve a custom account, update a custom account. Covers 89 operations with basic, oauth2 authentication.
Use for: I need to a custom account, I want to a custom account, Search for a custom account, Find all all accounts
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Quaderno helps you scale your business without stressing about taxes. Our powerful REST API solves all your tax compliance needs: - Accurate tax calculation on every sale, worldwide. - Billing with automatic invoices and credit notes. - Alerts for new tax obligations and registrations. - Tax reports by country or state. - Quaderno Checkout, if you don't have your own checkout. Here you can check o. The API exposes 89 endpoints secured with basic, oauth2 authentication.
Install Jentic One Beta
Connect the Quaderno API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quaderno 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%2Fquaderno.io%2Fquaderno" | 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%2Fquaderno.io%2Fquaderno" | 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 Quaderno API.
Retrieve a custom account
Update a custom account
Create a custom account
List all accounts
Access Quaderno API payments resources via REST API
Use Cases
Patterns agents use Quaderno API for, with concrete tasks.
★ Payments Operations
Use the Quaderno API to perform payments operations programmatically. The API provides 89 endpoints covering core functionality including retrieve a custom account, update a custom account, create a custom account.
Call GET /accounts/{id} to retrieve a custom account
Automated API features Management
Automate API features operations by combining multiple Quaderno API endpoints. Agents can update a custom account and then create a custom account in a single workflow.
Call PUT /accounts/{id} to update a custom account, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Quaderno 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 basic, oauth2 tokens manually.
Search Jentic for 'retrieve a custom account', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
89 endpoints — quaderno helps you scale your business without stressing about taxes.
METHOD
PATH
DESCRIPTION
GET
/accounts/{id}
Retrieve a custom account
PUT
/accounts/{id}
Update a custom account
POST
/accounts
Create a custom account
GET
/accounts
List all accounts
POST
/addresses
Create an address
GET
/addresses
List addresses
GET
/addresses/{id}
Retrieve an address
PUT
/addresses/{id}
Update an address
GET
/accounts/{id}
Retrieve a custom account
PUT
/accounts/{id}
Update a custom account
POST
/accounts
Create a custom account
GET
/accounts
List all accounts
POST
/addresses
Create an address
GET
/addresses
List addresses
GET
/addresses/{id}
Retrieve an address
PUT
/addresses/{id}
Update an address
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
Quaderno API
- AI-Aware (B-)63/100
46
Foundational Compliance65
Developer Experience & Jentic Compatibility60
AI-Readiness & Agent Experience87
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
46
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
69%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
39%
Example Density
How richly the API is illustrated with examples.
93%
Example Validity
Percentage of examples that conform to their schemas.
27%
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.
60
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
76%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
99%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
Summary Coverage
Coverage of summaries across operations/tags/info.
87
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
87%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
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 Quaderno by hand means resolving your account-specific quadernoapp.com host, handling its basic or OAuth2 auth, and shaping each request yourself. Through Jentic you install once, import the Quaderno API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Quaderno puts the account and address id in the URL path (/accounts/{id}, /addresses/{id}), so a rule can pin your agent to one account or address: it can read and update that record and nothing else. You choose the operations it may call, so ones like creating new accounts are not included unless you add them.
Credential isolation
Your Quaderno 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 'retrieve an account' or 'create a billing address', and Jentic returns the matching Quaderno 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 Quaderno API through Jentic.
What authentication does the Quaderno API use?
The Quaderno API uses basic, oauth2 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 retrieve a custom account with the Quaderno API?
Yes. Use the GET /accounts/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Quaderno 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 retrieve a custom account through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a custom account'. Jentic returns the matching Quaderno API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Quaderno API have?
The Quaderno API exposes 89 endpoints covering API features, changelog, registered jurisdictions operations.
Can I limit what my agent is allowed to do with the Quaderno API?
Yes. Because you run Jentic One yourself, your own rules decide which Quaderno operations and credential the agent may use. Quaderno carries the account and address id in the URL path, such as GET /accounts/{id} and PUT /addresses/{id}, so you can pin the agent to a single account or address and let it read and update only that record. You choose the operations it can call, so write actions like POST /accounts to create a new account stay off unless you explicitly add them.
GET STARTED