canonical: https://jentic.com/apis/mangoslab.org/mangoslab

# Mangoslab Nemonic Zapier API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Printers** — List of Nemonic devices attached to the authenticated account
- **Action** — Print job submission endpoint
- **AuthTest** — Verify the supplied OAuth or bearer credential is valid
- **Ping** — Service health check

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Zapier Natural Language Actions** — Trigger Nemonic prints as part of a wider multi-app Zap rather than a direct call.
- **n8n** — Self-hosted automation platform - alternative trigger surface for Nemonic prints.
- **Trello** — Source of card content that downstream prints can render to a Nemonic sticky note.

## FAQ

### 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.