Install Jentic One Beta

Connect the MoneyGram API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MoneyGram 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%2Fmoneygram.com%2Fmoneygram" | sh

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%2Fmoneygram.com%2Fmoneygram" | 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 MoneyGram API.

Quote the fees and exchange rate for a transfer transaction

Update a transfer's details and commit it to send

Run the same quote, update, and commit flow for a disbursement

Check the status of a transaction

Read supported countries, currencies, and enumerations

GET STARTED

Start building with MoneyGram API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MoneyGram API for, with concrete tasks.

★ Agent-Assisted Transfer

A finance assistant can walk a transfer from quote to send with human confirmation on the money-moving step. The agent quotes the transaction, updates the recipient details, and, once a person approves, commits it, so a supported send runs through the API while the commit stays a deliberate, reviewed action.

Quote a transfer, update its details, and commit it once a human approves

Transfer Status Tracking

A support agent can answer 'where is my transfer' without opening a console. It calls the status endpoint for a transaction, reads back the current state, and relays it to the customer, so a status question is answered from the live record rather than a stale note.

Fetch the status of a transaction and report its current state to the customer

Corridor and Rate Lookup

A planning agent can tell a user what a corridor supports and what it will cost before starting a transfer. It reads the countries, currencies, and FX-rate endpoints, and finds nearby pickup locations, so a question like 'can I send to this country and at what rate' is answered from reference data.

Read the supported countries, currencies, and current rate for a corridor and list nearby pickup locations

Key Endpoints

12 endpoints — the moneygram api creates and settles money transfers and their disbursements.

METHOD

PATH

DESCRIPTION

POST

/transfer/v1/transactions/{transactionID}/quote

Quote a transfer transaction

PUT

/transfer/v1/transactions/{transactionID}/commit

Commit a transfer to send

GET

/status/v1/transactions/

Check transaction status

GET

/reference-data/v1/countries

List supported countries

GET

/agent-locator/v1/locations

Find agent pickup locations

GET

/fxrate/v1/rates

Get current exchange rates

POST

/transfer/v1/transactions/{transactionID}/quote

Quote a transfer transaction

PUT

/transfer/v1/transactions/{transactionID}/commit

Commit a transfer to send

GET

/status/v1/transactions/

Check transaction status

GET

/reference-data/v1/countries

List supported countries

GET

/agent-locator/v1/locations

Find agent pickup locations

GET

/fxrate/v1/rates

Get current exchange rates

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the MoneyGram API by hand means handling its OAuth2 flow and sequencing the quote, update, and commit calls correctly for both transfers and disbursements. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the transfer, status, and reference-data operations.

Permission scoping

MoneyGram puts the transaction id in the URL path (/transfer/v1/transactions/{transactionID}), so a rule can scope your agent to one transaction and allow only the quote and status operations, keeping the commit step out of scope until you add it. You decide which operations are in scope, and every action is logged.

Credential isolation

Your MoneyGram OAuth2 token 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 'quote a money transfer' or 'check a transaction status', and Jentic returns the matching MoneyGram operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using MoneyGram API through Jentic.

What authentication does the MoneyGram API use?

The MoneyGram API authenticates with an OAuth2 access token, per its OpenAPI spec. When you call it through Jentic, that token is held by your own self-hosted instance and injected at execution time, so it never appears in the agent's prompt or logs.

Can I quote and commit a transfer with the MoneyGram API?

Yes. Post to the quote endpoint for a transaction to get its fees and rate, update the transaction details, then call the commit endpoint to send it. The disbursement endpoints follow the same quote, update, and commit sequence.

What are the rate limits for the MoneyGram API?

The OpenAPI spec for the MoneyGram API does not define rate limits. Check MoneyGram's partner documentation for the limits that apply to your credentials before running high-volume quoting or status polling.

Is there a MoneyGram API MCP server?

You don't need an MCP server to give your agent the MoneyGram API. Jentic connects it directly from the API Directory: import it, store the OAuth2 token once, and your agent calls the transfer, status, and reference-data operations without another server's tool definitions loaded into its context.

Can I limit what my agent is allowed to do with the MoneyGram API?

Yes. MoneyGram puts the transaction id in the URL path (/transfer/v1/transactions/{transactionID}), so a rule can scope your agent to one transaction and allow only the quote and status operations, leaving the commit step out of scope until you add it. The permitted set is yours to choose, and each action the agent takes is recorded.

How do I quote a transfer with the MoneyGram API through Jentic?

Search Jentic with an intent like 'quote a money transfer', and it returns the quote operation with its input schema so the agent submits the transaction and reads back the fees and rate. To run it on your own infrastructure, install Jentic One from its GitHub repo.

MoneyGram API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticPaymentsPayouts Transfersoauth212 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Quote, update, and commit MoneyGram money transfers and disbursements, check transaction status, and read reference data like countries, currencies, exchange rates, and pickup locations.

Use for: Quote the cost of sending a transfer, Commit a transfer to send it, Check the status of a transaction, Look up the supported currencies

Not supported: Covers transfer and disbursement quoting, sending, status, and the supporting reference data. Does not handle card processing, account management, or compliance screening.

The MoneyGram API creates and settles money transfers and their disbursements. For a transaction it quotes the fees and exchange rate, updates the transfer details, and commits it to send, with the same quote-update-commit flow available on the disbursement side. A status endpoint reports where a transaction stands, and reference-data endpoints return the supported countries, currencies, and enumerations. Agent-locator and FX-rate endpoints return pickup locations and current rates. All calls use an OAuth2 access token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

40%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MoneyGram API to your agent

Capabilities

Start building with MoneyGram API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MoneyGram API

Jentic AI Readiness Score

MoneyGram API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness