Moov API

Name: Moov API
Brand: Moov API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer12 EndpointsREST

For Agents

Onboard accounts, link bank accounts and cards, move money via transfers, and process refunds through the Moov payments platform.

Install Jentic One Beta

Connect the Moov API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moov 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Moov API.

Create and update Moov accounts representing the businesses or individuals you transact with

Link external bank accounts to a Moov account so it can send or receive ACH transfers

Create transfers between Moov accounts and read the resulting transfer state

GET STARTED

Start building with Moov API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Moov API, keeping it validated and agent-ready. Moov is a US payments platform that lets companies onboard accounts, link bank accounts and cards, move money between them, and handle refunds and disputes through a single API. The 12 endpoints in this build cover account creation and lookup, bank account linkage, transfer creation and listing, refund creation, and the broader resources (sources, cards, payment links, disputes, enrichment) the platform supports. Authentication is a bearer token.

Use Cases

Patterns agents use Moov API for, with concrete tasks.

★ Marketplace Payouts to Sellers

A marketplace creates a Moov account per seller, links each seller's bank account, and uses transfers to settle the seller's earnings on a recurring schedule. Each transfer has a unique id that the marketplace stores against its order ledger so reconciliation, refunds, and disputes can be traced back to specific orders.

Create a Moov transfer of 250 USD from the marketplace account acc_marketplace to seller account acc_seller_42 and confirm the transfer reached COMPLETED.

Embedded Wallet Money Movement

A SaaS app gives each customer an embedded wallet backed by a Moov account, lets them link a bank account through Moov, and uses transfers to credit and debit balances. The same primitives back features like topping up a balance, paying out earnings, and refunding a charge.

Add a bank account to Moov account acc_77 with the supplied routing and account numbers and confirm the bank account is linked.

Refund and Dispute Operations

Customer support tools call POST /accounts/{accountID}/refunds with the original transfer id when a customer requests their money back. Combined with dispute and transfer-list endpoints, support staff can see the full lifecycle of a payment from origination to refund or dispute resolution.

Refund Moov transfer transfer_123 in full from account acc_42 and confirm the refund was created.

AI Agent Money Movement Tooling

An operations agent uses Jentic to discover Moov account, transfer, and refund endpoints and runs them with vault-stored bearer tokens. Because Moov does not publish a public OpenAPI spec under this URL, Jentic's spec is the only structured way to drive the API from agent tooling without scraping the developer portal.

Search Jentic for 'create a Moov transfer', load the schema for POST /accounts/{accountID}/transfers, and execute a 10 USD transfer in the sandbox.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for moov api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/accounts

Create a Moov account

GET

/accounts

List accounts

GET

/accounts/{accountID}

Get account details

PATCH

/accounts/{accountID}

Update an account

POST

/accounts/{accountID}/bank-accounts

Link a bank account

POST

/accounts/{accountID}/transfers

Create a transfer

GET

/accounts/{accountID}/transfers/{transferID}

Get transfer details

POST

/accounts/{accountID}/refunds

Create a refund

POST

/accounts

Create a Moov account

GET

/accounts

List accounts

GET

/accounts/{accountID}

Get account details

PATCH

/accounts/{accountID}

Update an account

POST

/accounts/{accountID}/bank-accounts

Link a bank account

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Moov bearer tokens are stored encrypted in the Jentic vault. Jentic applies the Authorization: Bearer header at execution time so the raw token never enters the agent's context, even when the agent operates across many merchant accounts.

Intent-based discovery

Agents search Jentic by intent (e.g. 'move money between Moov accounts') and receive the matching Moov endpoint with its full input schema, including the accountID and transferID parameters.

Time to first call

Direct Moov integration: 2-4 days for auth, account onboarding, bank linkage, and transfer state handling. Through Jentic: under 1 hour to search, load the schema, and run the first sandbox transfer.

FAQs

Specific to using Moov API through Jentic.

Why is there no official OpenAPI spec for Moov API?

Moov does not publish an OpenAPI specification at this version. Jentic generates and maintains this spec so that AI agents and developers can call Moov API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Moov API use?

Moov uses bearer token authentication. Tokens are obtained from Moov's authentication flow and included as Authorization: Bearer on each request. Through Jentic the token is stored in the credential vault and applied at execution time.

Can I move money between Moov accounts with this API?

Yes. Call POST /accounts/{accountID}/transfers with the source, destination, and amount to create a transfer. Read GET /accounts/{accountID}/transfers/{transferID} or list transfers to monitor state and reconcile against your own ledger.

What are the rate limits for the Moov API?

Moov enforces per-account rate limits that vary by environment and are not declared in the spec. Treat HTTP 429 as a back-off signal and retry with exponential delay; for bulk operations stagger calls rather than firing them in parallel.

How do I issue a refund through Jentic?

Search Jentic for 'refund a Moov transfer', load the schema for POST /accounts/{accountID}/refunds, and execute it with the originating account id and the transfer id to refund. Jentic injects the bearer token automatically.

Can I link a bank account to a Moov account programmatically?

Yes. POST /accounts/{accountID}/bank-accounts accepts the routing and account number for the external bank, and the linked bank account becomes available as a source or destination for ACH transfers from that Moov account.

Moov API

Connect the Moov API to your agent

Capabilities

Start building with Moov API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs