Install Jentic One Beta

Connect the Nemonic Zapier API to your agent

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

List the Nemonic printers attached to the authenticated account

Submit a sticky-note print job containing text or image content

Verify the credential is still valid via the auth-test endpoint

Health-check the Nemonic Zapier service before triggering a print

Wire a Nemonic printer into a Zapier-style 'on event do print' automation

GET STARTED

Start building with Nemonic Zapier API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nemonic Zapier API for, with concrete tasks.

★ Print physical reminders from a task app

Knowledge workers want their daily tasks printed as a physical sticky note next to the keyboard. A Zap or scheduled automation pulls the day's tasks from a task manager and calls POST /v1/Print with the formatted text and the chosen Nemonic printer id from GET /v1/Printers. The result is a thermal-printed reminder without ink or cartridges.

Pull the user's three highest-priority tasks for today and submit them as a single print job to the user's primary Nemonic printer.

Label printing from inventory events

Small workshops use Nemonic for ad-hoc labels - bin tags, batch markers, packing slips. Inventory or order events trigger POST /v1/Print with the label text and the printer id, producing a printed label on demand. GET /v1/Printers picks the right device when more than one is paired with the account.

On a new order webhook, format a packing label and submit it to the warehouse Nemonic printer via POST /v1/Print.

Agent-driven physical output

An AI agent inside a productivity workflow can produce a physical artefact when it matters - meeting prep, a shopping list, an alert. Through Jentic, the agent searches by intent, picks the user's Nemonic printer from /v1/Printers, and submits the print to /v1/Print, all without holding the OAuth token in its prompt context.

Given a generated meeting agenda, list Nemonic printers, select the office printer, and submit the agenda as a sticky note print.

Key Endpoints

4 endpoints — mangoslab's nemonic is an inkless thermal printer for sticky notes and labels, and the nemonic zapier api is the small rest surface used by the nemonic zapier integration to discover and print to a user's nemonic device.

METHOD

PATH

DESCRIPTION

GET

/v1/AuthTest

Verify the credential is valid

GET

/v1/Ping

Service health check

GET

/v1/Printers

List the user's Nemonic printers

POST

/v1/Print

Submit a print job to a Nemonic printer

GET

/v1/AuthTest

Verify the credential is valid

GET

/v1/Ping

Service health check

GET

/v1/Printers

List the user's Nemonic printers

POST

/v1/Print

Submit a print job to a Nemonic printer

Why Jentic?

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

Setup

Wiring the Nemonic printer API by hand means running its OAuth 2.0 flow, keeping a bearer token fresh, and learning the /v1 print and printer-list endpoints yourself. Through Jentic you install once, import the Nemonic Zapier API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Nemonic print target travels in the request body rather than the URL path, so scoping is by operation: you limit the agent to the operations it needs, such as listing printers and sending a print, and leave out the auth or ping checks if you do not want them called. Every operation you allow is one you have chosen, so the agent stays inside that set.

Credential isolation

Your Nemonic OAuth token 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 'print a sticky note' or 'list available printers', and Jentic returns the matching Nemonic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Nemonic Zapier API through Jentic.

What authentication does the Nemonic Zapier API use?

Both bearer token and OAuth 2.0 are defined in the spec. The Zapier integration flow uses OAuth 2.0 to obtain a token tied to a Nemonic mobile-app account; bearer is the format the resulting token is sent in. Through Jentic the token is held encrypted in the vault and injected per call, so the agent never sees the raw value.

Can I send a print job to a specific Nemonic printer?

Yes. Call GET /v1/Printers to list the printers attached to the account, pick the printer id, then POST /v1/Print with the print payload referencing that printer. The print is dispatched to the chosen device rather than broadcast across all printers on the account.

What are the rate limits for the Nemonic Zapier API?

The spec does not publish rate limits. The service is sized for Zapier-style triggers (a small number of prints per minute per user), so high-frequency batch printing is likely to be throttled. Pace print jobs and back off on 429 responses.

How do I print a sticky note through Jentic?

Run pip install jentic, then search Jentic for 'print a sticky note on my nemonic'. Jentic returns the POST /v1/Print operation with its print-job schema, which you execute with the printer id (from /v1/Printers) and the content of the note.

Does the Nemonic Zapier API support label content beyond plain text?

The /v1/Print payload accepts the content the Zapier integration is designed for - short text and basic formatting suitable for a 50mm thermal sticky note. It is not a general-purpose printer SDK; complex layouts and high-resolution graphics are out of scope.

Is the Nemonic Zapier API free to use?

The API itself is free; you need a Nemonic device and a paired account. Mangoslab does not charge per print over the API, though Zapier charges separately for tasks consumed in their automation tier when the API is wired through a Zap.

Can I limit what my agent is allowed to do with the Nemonic Zapier API?

Yes. Because Jentic One is self-hosted, you decide which operations your agent may call, so you can allow it to list printers with GET /v1/Printers and submit a print with POST /v1/Print while leaving out the GET /v1/AuthTest and GET /v1/Ping checks if you do not want them touched. Scoping here is by operation, since the target printer travels in the print request body rather than the URL path, so the agent stays inside the exact set of endpoints you have chosen. Your Nemonic OAuth or bearer credential is stored by your own instance and injected at call time, so the agent never sees the raw token.

Mangoslab Nemonic Zapier API

Name: Nemonic Zapier API
Brand: Nemonic Zapier API
Availability: InStock

Community OpenAPI document · agent-readyIOTDevice Managementbearer, oauth24 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Discover a user's Nemonic thermal sticky-note printers and submit print jobs to them through a small bearer or OAuth 2.0 REST API.

Use for: Print a sticky note on my Nemonic printer with today's tasks, List the Nemonic printers on my account, Check that my Nemonic OAuth token is still valid, Send a label print job to a specific Nemonic printer id

Not supported: Does not handle high-resolution graphics, networked office printers, or shipping-label generation - use for short text prints to Nemonic thermal sticky-note devices only.

Mangoslab's Nemonic is an inkless thermal printer for sticky notes and labels, and the Nemonic Zapier API is the small REST surface used by the Nemonic Zapier integration to discover and print to a user's Nemonic device. The endpoints cover authentication test, ping, listing the user's printers, and submitting a print job. Authentication is bearer or OAuth 2.0, granted from the Nemonic mobile app account. The API is purpose-built for Zapier-style automations rather than a general-purpose printer SDK.

Jentic One on Github View OpenAPI Document