What authentication does the MoMo API use?

MoMo uses an API key sent in the X-API-Key request header. Obtain the key by calling POST /auth/token with merchant credentials. Through Jentic, both the merchant credentials and the resulting key are held encrypted in the credential vault so they never enter agent context.

Can I list merchant resources with the MoMo API?

Yes. After authenticating with POST /auth/token, call GET /resources to list resources for the merchant account, and GET /resources/{id} to retrieve a single resource by ID. The response shape is consistent across both endpoints.

What are the rate limits for the MoMo API?

MoMo does not document rate limits in this OpenAPI spec. Production rate limits are typically configured per merchant account on the MoMo developer portal at https://developers.momo.vn - confirm current limits there before running batch operations.

How do I get a MoMo access token through Jentic?

Run pip install jentic, search for 'authenticate to momo', load POST /auth/token, and execute it with the merchant credentials held in your Jentic One instance. Jentic returns the access token, which subsequent operations use automatically.

Is the MoMo API free?

Access to the API itself does not have a published flat fee - pricing for actual MoMo transactions is set by merchant agreement. Confirm with MoMo's merchant team for the commercial terms applicable to your account.

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

Yes. Because you run Jentic One yourself, your own rules decide which MoMo operations and credentials the agent may use, so you can allow only POST /auth/token and GET /resources while withholding anything else. Since MoMo puts the resource ID in the URL path at GET /resources/{id}, a rule can pin the agent to a single resource for lookups rather than the full list. The agent gets only the token exchange and resource reads you grant it.