How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
The 0x API v2 aggregates liquidity from on-chain DEXs and off-chain market makers across Ethereum and dozens of other EVM chains, returning the best executable price and a ready-to-sign transaction for a token swap. Two flavours are exposed: an Allowance Holder flow that uses a single approval contract, and a Permit2 flow that signs token allowances per trade. A separate Gasless endpoint set lets users trade without holding the native gas token by relaying signed messages. Designed for wallets, trading bots, and DeFi front ends that need consistent best-of-route pricing.
Jentic publishes the only available OpenAPI specification for 1Forge Finance APIs, keeping it validated and agent-ready. 1Forge provides real-time forex and cryptocurrency market data through a small set of focused endpoints covering live quotes, currency conversion, supported symbol lists, and forex market status. Agents can pull bid/ask/mid prices for currency pairs such as EUR/USD or BTCUSD, convert specific amounts between currencies on demand, and check whether the forex market is currently open before placing logic. The API is designed for low-friction integration: a single API key authenticates all requests and responses are flat JSON objects.
The UK Open Banking Account and Transaction API (AISP) is the standard interface that account-information service providers use to read PSU bank data from regulated UK banks. It defines 29 endpoints covering account access consents, account lists, balances, transactions, beneficiaries, direct debits, standing orders, statements, products, and parties. The flow uses two OAuth 2.0 schemes: TPP client credentials for consent setup and PSU authorization-code SCA for resource access. Every ASPSP that complies with the standard exposes the same operations under their own /open-banking/v4.0/aisp base path.
The National Bank of Greece Account and Transaction API implements the UK Open Banking Account and Transaction profile v3.1.5, providing AISP-style access to NBG retail and business accounts. Authorised third parties can request consent, list accounts, and read balances, transactions, statements, beneficiaries, parties, scheduled payments, and standing orders. The spec also exposes sandbox management endpoints for setting up and tearing down test datasets. Authentication combines OAuth 2.0 (client-credentials and authorisation-code flows) with a Client-Id header.
This NBG main spec is the canonical catalogue entry for the National Bank of Greece Account and Transaction API, implementing the UK Open Banking Account and Transaction profile v3.1.5. Authorised AISPs can read NBG accounts, balances, transactions, statements, beneficiaries, parties, scheduled payments, and standing orders, plus provision sandbox datasets for development. Authentication combines OAuth 2.0 (client-credentials and authorisation-code flows) with a Client-Id header.
The Vonage Account API (account) lets you manage a Vonage (formerly Nexmo) communications account programmatically. It exposes balance checks, auto-reload top-ups, default SMS and delivery-receipt callback configuration, registered email sender management, and full lifecycle control over the API secrets attached to each Vonage API key. The 8 endpoints cover the operational surface needed to keep a messaging or voice account funded, configured, and credentialed.
The Vonage Account API (account-api) lets you manage a Vonage (formerly Nexmo) communications account programmatically. It exposes balance checks, auto-reload top-ups, default SMS and delivery-receipt callback configuration, registered email sender management, and full lifecycle control over the API secrets attached to each Vonage API key. The 8 endpoints cover the operational surface needed to keep a messaging or voice account funded, configured, and credentialed.
Open Banking Platform PSD2 API - Account Information Summary The **NextGenPSD2** *Framework Version 1.3.3* offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and,. The API exposes 5 endpoints secured with oauth2 authentication.
Apideck Accounting is a unified API that maps a single schema for invoices, bills, payments, ledger accounts, customers, suppliers, and tax rates onto many downstream accounting platforms such as Xero, QuickBooks, Sage, NetSuite, and FreshBooks. The 95 operations cover the day-to-day finance objects most apps need plus reports like Balance Sheet, Profit and Loss, and Aged Debtors. Apideck routes each call through Apideck Vault, so customer credentials for the underlying platform stay in Apideck's vault instead of being passed in by the calling app.
Codat's Accounting API provides a unified interface for reading and writing accounting data across 20+ accounting platforms including QuickBooks, Xero, Sage, NetSuite, and FreeAgent. It standardises invoices, bills, journal entries, customers, suppliers, payments, and financial reports so a single integration maps to all supported systems. The API supports both pull operations (read normalised data from a linked company) and push operations (create or update records back into the source ledger). It is designed for fintech applications, lending platforms, and B2B SaaS products that need accounting data from their customers' books.
swaggerhub.nebulagts/accountingapi1 version 1.0.7. The API exposes 59 endpoints secured with apiKey authentication.
swaggerhub.nebulagts/accounting2api version 1.0.0. The API exposes 60 endpoints secured with apiKey authentication.
Jentic publishes the only available OpenAPI specification for Acrual API, keeping it validated and agent-ready. Acrual is a job management and invoicing platform for service businesses, and its API exposes 35 endpoints across clients, employees, jobs, quotes, invoices, purchase orders, suppliers, time entries, variations, hooks, integrations, and settings. Jobs can have files uploaded, folders created, and invoiced status retrieved. Authentication is bearer token, base URL is acrual.com/api/v1.0.
Jentic publishes the only available OpenAPI specification for Acrual API, keeping it validated and agent-ready. Acrual is a business management platform for manufacturing and construction businesses that exposes endpoints for clients, employees, jobs, quotes, invoices, purchase orders, time entries, suppliers, and variations. The API supports webhook subscriptions and third-party integration handshakes, so back-office tools can react to changes in jobs and invoices in near real time. Authentication uses bearer tokens, and the spec covers 46 operations across 11 resource groups under the /v1.0 path prefix.
Jentic publishes the only available OpenAPI specification for Addepar API, keeping it validated and agent-ready. Addepar is a wealth management technology platform used by RIAs, family offices, and large advisory firms to track multi-asset-class portfolios. The API exposes entities (clients, accounts, holdings), portfolio query endpoints for performance and exposure analysis, users and groups for permissions, and files for document storage. Authentication combines an Addepar-Firm header (API key) with HTTP Basic credentials, scoping each call to a specific firm tenant.
Jentic publishes the only available OpenAPI specification for Afterbanks API, keeping it validated and agent-ready. Afterbanks is a Spanish open-banking aggregator that standardises real-time access to bank account data across Spanish, Portuguese, and Latin American banks. The API exposes a small surface — bank form discovery, user account info, and the V3 bank-data service — that lets fintech and lending apps fetch transactions and balances from end-customer bank accounts after consent.
Jentic publishes the only available OpenAPI specification for Afterbanks API, keeping it validated and agent-ready. This is the apis.guru-rooted variant of the Afterbanks open-banking aggregator, exposing the same three-endpoint surface — bank form discovery, the authenticated user profile, and the V3 bank-data service. Use it to pull standardised account, balance, and transaction data from Spanish, Portuguese, and Latin American banks after the end customer completes a consent flow.
La estandarización de la conexión con cualquier banco en tiempo real. The API exposes 30 endpoints.
**AlayaCare IDs:** The following terms are used to reference IDs that identify resources in AlayaCare: - id - visit_id - premium_id - visit_premium_id - employee_id - cost_centre_id - client_id **External IDs** The following terms are used to reference IDs that identify resources systems external to AlayaCare: - employee_external_id - client_external_id External IDs are required to be unique. No o. The API exposes 65 endpoints secured with basic authentication.
SoftBank Robotics developer API for humanoid robots and automation. The API exposes 3 endpoints secured with apiKey authentication.
Jentic publishes the only available OpenAPI specification for Alegra API, keeping it validated and agent-ready. Alegra is an accounting and invoicing platform widely used by SMBs across Latin America and Spain. The REST API exposes invoices, items, contacts (customers and suppliers), payments, estimates, credit notes, bank accounts, and chart-of-accounts categories. Authentication uses HTTP basic auth with the user's Alegra email and an API token from the Alegra account.
Jentic publishes the only available OpenAPI specification for Aletheia Financial API, keeping it validated and agent-ready. Aletheia provides real-time stock market and cryptocurrency data through a small, focused REST surface. The API exposes a stock data endpoint, a crypto quote endpoint, an account consumption endpoint for tracking quota usage, and a version probe. Authentication uses an API key passed in the 'key' header on every request.
Jentic publishes the only available OpenAPI specification for the Algod REST API, keeping it validated and agent-ready. The Algod API is the primary interface to an Algorand node, exposing 56 endpoints for reading account state, application and asset data, blocks, and ledger deltas, plus submitting transactions and running TEAL programs. It is the lowest-level on-chain interface for Algorand and is what wallets, dApps, and indexers call to interact with the network. Public infrastructure like AlgoNode hosts mainnet and testnet endpoints under the same spec.
Jentic publishes the only available OpenAPI specification for the Aliaddo API, keeping it validated and agent-ready. Aliaddo is a Colombian accounting and business management platform, and its API exposes 17 endpoints covering invoicing, sales orders, sales remissions, accounting entries, cost centers, products, warehouses, and contacts. The API is bearer-token authenticated and is aimed at integrators automating billing, inventory, and contact sync between Aliaddo and external commerce systems.
Jentic publishes the only available OpenAPI specification for Allianz Trade API, keeping it validated and agent-ready. Allianz Trade (formerly Euler Hermes) is a global trade credit insurer, and the API exposes buyer search, buyer risk lookup, cover requests, claims filing, and portfolio exposure reporting. Authentication uses OAuth 2.0 client credentials, suitable for system-to-system integration in finance and treasury workflows. The endpoint set is focused on the credit-cover lifecycle rather than general policy administration.
The Alpaca Market Data API provides real-time and historical market data for US equities, options, crypto, crypto perpetual futures, and foreign exchange. Endpoints cover historical bars, quotes, trades, and auctions for stocks, options chains and snapshots, crypto bars and orderbooks, forex rates, screeners for movers and most-actives, news articles, corporate actions, and company logos. Authentication uses APCA-API-KEY-ID and APCA-API-SECRET-KEY headers. Both production and sandbox endpoints are exposed.
The Alpaca Trading API is the self-directed trading surface of the Alpaca platform, designed for individual developers and algorithmic traders running their own brokerage account. It exposes orders, positions, watchlists, account configurations, account activities, market calendar and clock, assets, options contracts, corporate actions, crypto funding wallets, and portfolio history. Authentication uses APCA-API-KEY-ID and APCA-API-SECRET-KEY headers, and live and paper environments are exposed at api.alpaca.markets and paper-api.alpaca.markets respectively. With 44 endpoints, this API is focused on trading, not on opening or managing customer accounts.
Jentic publishes the only available OpenAPI specification for Alpha Vantage API, keeping it validated and agent-ready. Alpha Vantage exposes free and premium market-data endpoints for stocks, options, forex, crypto, commodities, economic indicators, and over 50 technical indicators, all served from a single /query path that selects the dataset via a 'function' parameter. Authentication is by apikey query string, and the catalogue spans realtime quotes, historical OHLC, fundamentals, news sentiment, and macro series. The API is widely used for trading research, dashboarding, and lightweight backtesting.
Jentic publishes the only available OpenAPI specification for AlphaInsider Trading API, keeping it validated and agent-ready. AlphaInsider is a trading-strategy marketplace for crypto and equities, and this integration exposes a single webhook endpoint that brokers and copy-trading platforms call to forward strategy trade signals into AlphaInsider for paper-trading tracking. No live orders are executed through the API; it is a one-way ingest channel for paper-trade fills used to track strategy performance.
Jentic publishes the only available OpenAPI specification for Altoviz API, keeping it validated and agent-ready. Altoviz is a free invoicing and accounting platform that exposes 34 REST endpoints across customers, suppliers, products, sale invoices, purchase invoices, receipts, customer families, settings, and users. Teams use it to push invoices and receipts from line-of-business systems, sync customer and supplier records, and pull settings such as tax codes and numbering rules. Authentication is a single x-api-key header issued from the Altoviz dashboard.
Jentic publishes the only available OpenAPI specification for Amdoren Currency API, keeping it validated and agent-ready. The Amdoren Currency API is a free currency conversion service supporting more than 150 fiat currencies. Its single GET endpoint returns the converted amount between a source and destination currency at the current exchange rate, authenticated by an api_key query parameter against www.amdoren.com/api. Typical consumers are budgeting apps, travel tools, e-commerce checkouts, and AI agents that need a low-friction conversion lookup without the overhead of a multi-endpoint FX provider.
Jentic publishes the only available OpenAPI specification for ANZ Developer API, keeping it validated and agent-ready. ANZ is one of Australia's four major banks and exposes a developer API for accessing customer accounts, listing transactions, and submitting payments. The current surface area is intentionally small (three endpoints) and is intended for accredited partner integrations under Australia's Consumer Data Right and similar partner programs. Authentication is an API key in the Authorization header.