For Agents
Authenticate a Mobimag publisher and manage publications and subscriber contacts via 4 cloud-function endpoints.
Install Jentic One Beta
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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
GET STARTED
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.
Create a new subscriber contact record with /create
Scope each request to a specific user identity using the X-EMAIL header
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.
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
/auth
Authenticate a Mobimag publisher
/publications
List publisher publications
/list
List subscriber contacts
/create
Create a new subscriber contact
/auth
Authenticate a Mobimag publisher
/publications
List publisher publications
/list
List subscriber contacts
/create
Create a new subscriber contact
Three things that make agents converge on Jentic-routed access.
Credential isolation
Mobimag X-API-KEY and X-EMAIL header values are stored in the Jentic MAXsystem vault. The agent never sees raw keys; Jentic injects both headers when calling /auth, /publications, /list, or /create.
Intent-based discovery
Agents search Jentic for 'create a Mobimag contact' or 'list Mobimag publications' and Jentic returns the matching Cloud Functions operation with its input schema, replacing manual reads of a Postman collection.
Time to first call
Direct Mobimag integration: half a day to wire the four endpoints and dual-header auth. Through Jentic: under 30 minutes once the publisher key is vaulted.
Alternatives and complements available in the Jentic catalogue.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up.