Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moffin 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%2Fsandbox.moffin.mx%2Fsandbox-moffin-mx" | 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%2Fsandbox.moffin.mx%2Fsandbox-moffin-mx" | 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 Moffin API.
Profiles_getById
Profiles_updateProfile
Profiles_createProfile
Profiles_listWithPagination
Profiles_createMultiple
GET STARTED
Profiles_queryProfileServices
Profiles_getMoffinReducedInfo
Patterns agents use Moffin API for, with concrete tasks.
★ AI and Machine Learning Operations
Use the Moffin API to perform ai ml operations programmatically. The API provides 36 endpoints covering core functionality including profiles_getbyid, profiles_updateprofile, profiles_createprofile.
Call GET /api/v1/profiles/{id} to profiles_getbyid
Automated Query data sources Management
Automate query data sources operations by combining multiple Moffin API endpoints. Agents can profiles_updateprofile and then profiles_createprofile in a single workflow.
Call PUT /api/v1/profiles/{id} to profiles_updateprofile, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Moffin API 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 none tokens manually.
Search Jentic for 'profiles_getbyid', load the operation schema, and execute with Jentic-managed credentials
36 endpoints — introduction moffin allows you to validate and evaluate the credit profile of your clients in an instant.
METHOD
PATH
DESCRIPTION
/api/v1/profiles/{id}
Profiles_getById
/api/v1/profiles/{id}
Profiles_updateProfile
/api/v1/profiles
Profiles_createProfile
/api/v1/profiles
Profiles_listWithPagination
/api/v1/profiles/info
Profiles_createMultiple
/api/v1/profiles/{id}/query
Profiles_queryProfileServices
/api/v1/profiles/{id}/info
Profiles_getMoffinReducedInfo
/api/v1/report
Reports_getData
/api/v1/profiles/{id}
Profiles_getById
/api/v1/profiles/{id}
Profiles_updateProfile
/api/v1/profiles
Profiles_createProfile
/api/v1/profiles
Profiles_listWithPagination
/api/v1/profiles/info
Profiles_createMultiple
/api/v1/profiles/{id}/query
Profiles_queryProfileServices
/api/v1/profiles/{id}/info
Profiles_getMoffinReducedInfo
/api/v1/report
Reports_getData
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Moffin API by hand means reading the reference to map its profile and report endpoints on the sandbox or production moffin.mx host and handling paging and retries yourself. Through Jentic you install once, import Moffin from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Moffin puts the profile id in the URL path (/api/v1/profiles/{id}), so a rule can pin your agent to specific profiles: it can read or update the ones you allow and nothing else. You choose the operations it may call, so writes like creating a profile are not included unless you add them.
Credential isolation
Your Moffin 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 'get a profile by id' or 'get a report', and Jentic returns the matching Moffin 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.
Specific to using Moffin API through Jentic.
What authentication does the Moffin API use?
The Moffin API uses no 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.
Can I profiles_getbyid with the Moffin API?
Yes. Use the GET /api/v1/profiles/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Moffin API?
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 profiles_getbyid through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'profiles_getbyid'. Jentic returns the matching Moffin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Moffin API have?
The Moffin API exposes 36 endpoints covering query data sources, profiles, form operations.
Can I limit what my agent is allowed to do with the Moffin API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Moffin operations and credentials your agent may use. Moffin puts the profile id in the URL path (/api/v1/profiles/{id}), so you can pin the agent to specific profiles and let it only read (GET /api/v1/profiles/{id}) or update (PUT /api/v1/profiles/{id}) the ones you allow. You choose the operations it may call, so writes such as creating a profile or querying profile services stay off unless you explicitly grant them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically profiles_getbyid, profiles_updateprofile. Covers 36 operations.
Use for: I need to profiles_getbyid, I want to profiles_updateprofile, Search for profiles_createprofile, Find all profiles_listwithpagination
Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.
Introduction Moffin allows you to validate and evaluate the credit profile of your clients in an instant. Consult and automatically evaluate their financial information. Moffin API is implemented as a [REST API](https://en.wikipedia.org/wiki/Representational_State_Transfer) architecture. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON responses, an. The API exposes 36 endpoints.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>