Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OCT/AFT, 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%2Fswaggerhub.quiputech%2Foctaft" | 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%2Fswaggerhub.quiputech%2Foctaft" | 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 OCT/AFT API.
Access OCT/AFT resources via REST API
Manage developer tools data programmatically
Integrate OCT/AFT into automated workflows
Query and filter OCT/AFT records by parameters
Monitor OCT/AFT operational status and events
GET STARTED
Patterns agents use OCT/AFT API for, with concrete tasks.
★ Developer Tools Operations
The API provides 2 endpoints for developer tools operations.
Execute a primary operation against the OCT/AFT
Data Retrieval and Monitoring
Query OCT/AFT resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary OCT/AFT endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call OCT/AFT 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 apiKey, basic tokens manually.
Search Jentic for 'oct/aft', load the operation schema, and execute with Jentic-managed credentials
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the OCT/AFT API by hand means handling both its authorization header key and basic auth, and coding retries yourself. Through Jentic you install once, import the OCT/AFT API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The OCT/AFT API carries transfer details in the request body, not in the URL path, so you limit the agent to the operations it needs and leave out the rest. Every operation the agent can call is one you chose to allow.
Credential isolation
Your OCT/AFT credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'submit an original credit transfer' or 'submit an account funding transaction', and Jentic returns the matching OCT/AFT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using OCT/AFT API through Jentic.
What authentication does the OCT/AFT use?
The OCT/AFT uses apiKey, basic 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.
What are the rate limits for the OCT/AFT?
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 use oct/aft through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use oct/aft'. Jentic returns the matching OCT/AFT operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the OCT/AFT have?
The OCT/AFT exposes 2 endpoints covering oct, p2p operations.
Does the OCT/AFT support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the OCT/AFT API?
Yes. Jentic One is self-hosted, so you set the rules that decide which OCT/AFT operations your agent may call and which stored credentials it may use. Because the transfer details ride in the request body rather than the URL path, you can allow only the operations the agent needs, such as submitting an original credit transfer or an account funding transaction, and leave the rest out. Every operation the agent can reach is one you chose to permit.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access OCT/AFT resources. Covers 2 operations with apiKey, basic authentication.
Use for: I need to integrate with OCT/AFT, Find available developer tools operations, Get the current status of OCT/AFT resources, List all records from OCT/AFT
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
VisaNet OCT/AFT Project. Related to PET-1234. The API exposes 2 endpoints secured with apiKey, basic authentication.