What authentication does the MIP REST API use?

The MIP REST API authenticates with a `token` query parameter on every request. Through Jentic, the token is stored in the encrypted vault and appended to the URL at execution time, so agent code and prompts never include the raw secret in logs or URL strings.

What is the difference between /AddContactData_q and /AddContactData_t?

The `_q` suffix denotes the queued variant - the request is accepted and processed asynchronously, suited to high-volume batch ingestion. The `_t` suffix denotes the transactional variant - the request is processed synchronously and is suited to user-driven, time-sensitive writes.

How do I search for contacts through Jentic?

Search Jentic for 'search contacts in MIP', load the GET /Search_t schema, and execute it with the search parameters. Chain GET /GetContact_t for the top match to retrieve the full contact record in the same agent run.

Which reference data endpoints does MIP expose?

MIP exposes reference endpoints for countries (/RefCountries_t), genders (/RefGenders_t), languages (/RefLanguages_t), indicator types (/RefIndicators_t), legal forms (/RefLegalFormCodes_t), unique ID codes (/RefUniqueIDCodes_t), and per-entity attribute codes and types for individuals, relen, and social entries.

What are the rate limits for the MIP REST API?

The published spec does not document explicit rate limits. Treat the API as throttled in production, prefer the /AddContactData_q queued endpoint for bulk writes, and contact MIP support for account-specific limits before running large imports.

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

Yes. Because you run Jentic One yourself, your own rules decide which MIP operations and credentials the agent can use, so you allow only the endpoints a given task needs. MIP addresses contacts through request parameters rather than a resource id in the URL path, so you scope by operation: grant read-only calls such as GET /Search_t, GET /GetContact_t, and the reference lookups like /RefCountries_t and /RefLegalFormCodes_t, while leaving write operations such as POST /AddContactData_t and /AddContactData_q out of the allowed set unless you include them. This keeps an agent that only needs to search or validate contacts from ever adding or queuing new records.