Install Jentic One Beta

Connect the Mobimag Contacts API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mobimag Contacts 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%2Fmobimag.app%2Fmobimag-app" | 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%2Fmobimag.app%2Fmobimag-app" | 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 Mobimag Contacts API.

Authenticate a Mobimag publisher via the /auth endpoint using X-API-KEY and X-EMAIL headers

List the publications available under the authenticated publisher with /publications

Retrieve the contact list for a publisher's subscribers via /list

Create a new subscriber contact record through /create

Scope subscriber operations to a specific user via the X-EMAIL header

GET STARTED

Start building with Mobimag Contacts API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mobimag Contacts API for, with concrete tasks.

★ Subscriber import for a digital magazine

Publishers migrating an existing reader list onto Mobimag iterate over their export and POST each row to /create with the X-API-KEY header for the publisher and the X-EMAIL header for the reader. The minimal four-endpoint surface keeps the integration simple and deployable as a one-off migration script.

Iterate over a CSV of subscriber emails and POST each one to /create with X-API-KEY for the publisher and X-EMAIL set to the subscriber's address.

Publication catalog lookup

Front-end clients call /publications to render the catalogue of magazines available under the authenticated publisher, then use /list to show which contacts have access. This pattern keeps publisher-side logic out of the client and lets the cloud function enforce the X-API-KEY scope server-side.

GET /publications with the publisher's X-API-KEY, render the returned titles, then GET /list to fetch the associated contacts.

Agent integration via Jentic

An AI assistant for a Mobimag publisher can search Jentic for 'create a Mobimag contact', load the /create operation schema, and execute the call without exposing the X-API-KEY. The agent can chain into /publications and /list to give a full picture of catalogue and subscribers in a single conversation.

Search Jentic for 'create a Mobimag contact', load the /create schema, and execute it with the new subscriber's email.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/auth

Authenticate a Mobimag publisher

GET

/publications

List publisher publications

GET

/list

List subscriber contacts

POST

/create

Create a new subscriber contact

POST

/auth

Authenticate a Mobimag publisher

GET

/publications

List publisher publications

GET

/list

List subscriber contacts

POST

/create

Create a new subscriber contact

Why Jentic?

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

Setup

Wiring the Mobimag Contacts API by hand means handling its API key auth, running the publisher /auth step, and mapping subscriber list and create calls yourself. Through Jentic you install once, import the Mobimag Contacts API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Mobimag's publisher and contact targets travel in the request body rather than the URL path, so scope your agent by limiting it to the operations it needs, such as listing publications and reading the contact list. You leave out contact creation so the agent reads subscriber data without adding new contacts.

Credential isolation

Your Mobimag API key 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 'list Mobimag publications' or 'read the subscriber contact list', and Jentic returns the matching Mobimag operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mobimag Contacts API through Jentic.

Why is there no official OpenAPI spec for Mobimag Contacts API?

Mobimag does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mobimag Contacts API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Mobimag Contacts API use?

The API uses two apiKey headers: X-API-KEY identifies the publisher and X-EMAIL scopes the request to a specific user identity. Through Jentic both header values are stored in your Jentic One instance and injected at execution time.

Can I list all publications for a Mobimag publisher?

Yes. Call GET /publications with the publisher's X-API-KEY. The endpoint returns the publications attached to that publisher account, which you can then cross-reference against the contacts returned by /list.

What are the rate limits for the Mobimag Contacts API?

The OpenAPI specification does not declare rate limits, and Mobimag does not publish them. Treat HTTP 429 responses as the back-off signal and contact Mobimag if you plan a large bulk import.

How do I create a Mobimag subscriber contact through Jentic?

Run pip install jentic, search Jentic for 'create a Mobimag contact', load the /create schema, and execute it with the new subscriber's email. Jentic injects the X-API-KEY and X-EMAIL headers from the vault.

Is the Mobimag Contacts API free to use?

Mobimag is a commercial digital magazine platform; API access is gated by publisher accounts on Mobimag. There is no public free tier. Get started with Jentic One, the self-hosted execution layer.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the four Mobimag operations the agent may call and which credentials it may use. You can allow read-only access by scoping the agent to GET /publications and GET /list while leaving out POST /create, so it can read publications and the subscriber contact list without adding new contacts. Since Mobimag's publisher and contact targets travel in the request body rather than the URL, operation-level scoping is how you keep the agent inside its intended boundary.

Mobimag App Mobimag Contacts API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMediaContent DeliveryapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Authenticate a Mobimag publisher and manage subscriber contacts and publications via 4 cloud-function endpoints.

Use for: I need to authenticate a Mobimag publisher, List all Mobimag publications available to my account, Retrieve the contact list for a Mobimag publication, Create a new Mobimag subscriber contact

Not supported: Does not handle email delivery, payment processing, or content publishing - use for Mobimag publisher authentication and subscriber contact management only.

Jentic publishes the only available OpenAPI specification for Mobimag Contacts API, keeping it validated and agent-ready. Mobimag is a digital magazine publishing platform that lets publishers manage subscriber contacts and the publications those contacts can access. The Contacts API exposes four endpoints for authenticating a publisher, listing publications, listing existing contacts, and creating new contact records, deployed as a Google Cloud Function under us-central1-mobimagprod.cloudfunctions.net/contacts. Authentication uses two API key headers: X-API-KEY for the publisher and X-EMAIL to scope the request to a specific user identity.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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: A-Signals: 4

56%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

61%

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: C-Signals: 1

50%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Mobimag Contacts API to your agent

Capabilities

Start building with Mobimag Contacts API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mobimag App Mobimag Contacts API

Jentic AI Readiness Score

Mobimag Contacts 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