Install Jentic One Beta

Connect the Mobimag API to your agent

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

Authenticate a Mobimag publisher through the /auth endpoint with X-API-KEY and X-EMAIL headers

List the publications managed by the authenticated publisher via /publications

Retrieve the publisher's subscriber contact list at /list

Create a new subscriber contact record with /create

Scope each request to a specific user identity using the X-EMAIL header

GET STARTED

Start building with Mobimag API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mobimag API for, with concrete tasks.

★ Subscriber list maintenance

Publishers add new subscribers as they sign up by POSTing to /create with X-API-KEY for the publisher and X-EMAIL for the new reader. Periodic GETs to /list keep an external CRM in sync with the Mobimag subscriber list, and the cloud-function backend enforces publisher scoping server-side.

POST a new subscriber to /create with the publisher's X-API-KEY and the reader's X-EMAIL, then GET /list to confirm the row was created.

Catalogue rendering for a publisher portal

A publisher portal calls /publications to render the catalogue of magazines tied to the authenticated publisher, then /list to show subscriber counts per publication. The four-endpoint surface keeps the portal lightweight and lets it ship without a heavier backend in front of Mobimag.

GET /publications, render the returned magazine titles in the publisher dashboard, and call /list to enrich each row with the subscriber count.

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 then chain into /publications and /list to give a complete picture of the publisher's catalogue and audience.

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

Key Endpoints

4 endpoints — mobimag is a platform for publishing and monetising digital magazines, with subscriber contacts and publications managed through a small cloud functions api.

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 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 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 API through Jentic.

What authentication does the Mobimag API use?

Mobimag uses two apiKey headers: X-API-KEY identifies the publisher and X-EMAIL pins the request to a specific user. Through Jentic, both header values are stored in your Jentic One instance and injected automatically when an agent executes a call.

Can I list all subscriber contacts for a Mobimag publisher?

Yes. GET /list with the publisher's X-API-KEY returns the existing subscriber contacts. The same scoping headers are used by /create when adding a new subscriber to that publisher's list.

What are the rate limits for the Mobimag API?

The specification does not declare rate limits and Mobimag does not publish them. Treat HTTP 429 responses as the signal to back off, and contact Mobimag before running 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.

Does the Mobimag API support deleting or updating contacts?

The OpenAPI specification covers /auth, /publications, /list, and /create only. Update and delete operations are not part of this published surface; for those flows, contact Mobimag directly.

Is the Mobimag API free to use?

Mobimag is a commercial digital magazine platform; API access is gated by paid publisher accounts. 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 API?

Yes. Because you run Jentic One yourself, your own rules decide which Mobimag operations and credentials the agent may use. You can allow it to authenticate and only read data by permitting the /publications and /list operations while withholding /create, so the agent lists publications and reads the subscriber contact list without adding new contacts. The publisher and contact targets travel in the request body rather than the URL path, so this operation-level scoping is how you control the agent's reach.

Mobimag API

Name: Mobimag API
Brand: Mobimag API
Availability: InStock

Community OpenAPI document · agent-readyMediaContent DeliveryapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to authenticate a Mobimag publisher, List all Mobimag publications for my publisher account, Retrieve the subscriber contact list for a Mobimag publisher, 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.

Mobimag is a platform for publishing and monetising digital magazines, with subscriber contacts and publications managed through a small Cloud Functions API. The four-endpoint surface lets publishers authenticate, list their publications, list subscriber contacts, and create new contact records. Authentication is by two API key headers: X-API-KEY identifies the publisher and X-EMAIL pins the request to a specific user identity.

Jentic One on Github View OpenAPI Document

Connect the Mobimag API to your agent

Capabilities

Start building with Mobimag API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mobimag API