Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DTX Pro - 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%2Fdestaxa.com%2Fdestaxa" | shStep 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%2Fdestaxa.com%2Fdestaxa" | 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.
What an agent can do with DTX Pro - API.
Retrieve sales details and summaries for a reconciliation period
Chart how sales evolve over time
Read a receivables calendar with summaries, details, and daily totals
Break down receivables per sale and view consolidated totals
List filter options for transaction categories, card brands, and acquirers
GET STARTED
Patterns agents use DTX Pro - API for, with concrete tasks.
★ Agent-Driven Reconciliation Reporting
An AI agent prepares a reconciliation report by pulling sales details and the receivables calendar for a period, then scoping both by acquirer and card brand using the filter endpoints. The agent returns daily totals and a consolidated view, so a finance assistant can show what was sold and what is still owed without opening the DTX Pro dashboard.
Retrieve sales details and the receivables calendar summary for a date range, filtered by a chosen acquirer, and return the daily totals
Receivables Forecasting
Project upcoming cash flow by reading the receivables calendar's daily totals and consolidated figures. A treasury tool can show when acquirer payouts are expected and how much, turning the reconciliation data into a forward view of receivables.
Read the receivables calendar daily totals for the next 30 days and return the expected payout per day
Filter-Scoped Analytics
Drive dashboards that slice sales and receivables by transaction category, card brand, and acquirer. The filter endpoints list the valid options first, so an analytics tool offers only real choices before requesting the matching sales or receivables data.
List the available acquirers and card brands, then pull the sales summary scoped to one acquirer
12 endpoints — the destaxa dtx pro api reports on card payment reconciliation: it returns sales records and the receivables a merchant is owed by their acquirers.
METHOD
PATH
DESCRIPTION
/sales/details
Sales details for a period
/sales/details/summary
Sales details summary
/sales/analytics/evolution-graph
Sales evolution over time
/receivables/calendar/summary
Receivables calendar summary
/receivables/calendar/daily-totals
Daily receivables totals
/receivables/calendar/consolidated
Consolidated receivables view
/filters/acquirers
List acquirers to filter by
/filters/brands
List card brands to filter by
/sales/details
Sales details for a period
/sales/details/summary
Sales details summary
/sales/analytics/evolution-graph
Sales evolution over time
/receivables/calendar/summary
Receivables calendar summary
/receivables/calendar/daily-totals
Daily receivables totals
/receivables/calendar/consolidated
Consolidated receivables view
/filters/acquirers
List acquirers to filter by
/filters/brands
List card brands to filter by
What agents get from Jentic-routed access to this vendor.
Setup
By hand you obtain a JWT bearer token, set the Authorization header, learn the sales and receivables report shapes, and fetch filter options before a query returns the right slice. Through Jentic you connect once from the API Directory and your agent calls the reports by intent.
Permission scoping
Every operation reads reconciliation data, so you grant your agent only the reports it needs, such as sales summaries and receivables totals while leaving out per-sale breakdowns. Every call is logged for audit.
Credential isolation
Your JWT bearer token is stored encrypted on your own Jentic One instance and injected into the Authorization header at execution time, never placed in the agent's prompt, logs, or context. You rotate or revoke it in one place.
Intent-based discovery
Agents search Jentic by intent such as 'receivables calendar summary' or 'sales details', and Jentic returns the matching Destaxa operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using DTX Pro - API through Jentic.
What authentication does the Destaxa DTX Pro API use?
It uses an HTTP bearer token in JWT format: every request carries a bearer credential in the Authorization header. Through Jentic, your own Jentic One instance stores that token encrypted and attaches it to each call rather than exposing it to the agent.
Can I scope reconciliation data to one acquirer or card brand?
Yes. The filter endpoints list the available transaction categories, card brands, and acquirers, and you pass those values when requesting sales or receivables data. That lets a report cover a single acquirer, a single brand, or the whole account.
What are the rate limits for the Destaxa DTX Pro API?
The OpenAPI spec does not state rate limits. Check the official Destaxa documentation at https://destaxa.com/ for current limits before pulling large reconciliation reports.
How do I pull reconciliation data through Jentic?
Add the Destaxa DTX Pro API from the Jentic API Directory and connect your token once. Your agent then searches by intent such as 'receivables calendar summary' and calls the matching operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit which Destaxa operations my agent is allowed to call?
Yes. Every operation reads reconciliation data, so you grant your agent only the reports it needs, such as sales summaries and receivables totals while leaving out the rest. Every call the agent makes is logged, so you can audit exactly which reports it ran.
Is there a Destaxa DTX Pro MCP server?
You don't need an MCP server to use Destaxa DTX Pro with your agent. Jentic connects it directly from the API Directory: import it, connect your token once, and your agent can pull sales and receivables data without another server loading tool definitions into its context.
Know of an official OpenAPI document? Contribute it →
For Agents
Report on card payment reconciliation with Destaxa DTX Pro: pull sales details and summaries, chart sales evolution, and read a receivables calendar with daily totals and breakdowns. Lists filter options for categories, brands, and acquirers.
Use for: Get the sales details for last month, Show the receivables calendar summary, I want the daily totals of receivables, List the acquirers I can filter by
Not supported: Does not process payments, issue invoices, or move funds. Use for reconciling card sales and reporting receivables through Destaxa only.
The Destaxa DTX Pro API reports on card payment reconciliation: it returns sales records and the receivables a merchant is owed by their acquirers. You pull sales details and summaries, chart how sales evolve over time, and read a receivables calendar with summaries, daily totals, per-sale breakdowns, and consolidated views. Filter endpoints list the transaction categories, card brands, and acquirers available to scope a query, so a finance tool can slice reconciliation data the way it needs.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>