Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stannp Direct Mail 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%2Fstannp.com%2Fstannp" | shStep 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%2Fstannp.com%2Fstannp" | 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 Stannp Direct Mail API.
Get user account information
List recipients
Create a new recipient
Delete a recipient
Import recipients from a data file
GET STARTED
Patterns agents use Stannp Direct Mail API for, with concrete tasks.
★ Marketing Operations
Use the Stannp Direct Mail API to perform marketing operations programmatically. The API provides 29 endpoints covering core functionality including get user account information, list recipients, get a single recipient.
Call GET /user/info to get user account information
Automated Campaigns Management
Automate campaigns operations by combining multiple Stannp Direct Mail API endpoints. Agents can list recipients and then get a single recipient in a single workflow.
Call GET /recipients/list to list recipients, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Stannp Direct Mail API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic tokens manually.
Search Jentic for 'get user account information', load the operation schema, and execute with Jentic-managed credentials
29 endpoints — api for sending direct mail (postcards, letters), managing recipients, groups, and campaigns through the stannp platform.
METHOD
PATH
DESCRIPTION
/user/info
Get user account information
/recipients/list
List recipients
/recipients/get/{id}
Get a single recipient
/recipients/new
Create a new recipient
/recipients/delete
Delete a recipient
/recipients/import
Import recipients from a data file
/groups/list
List all groups
/groups/new
Create a new group
/user/info
Get user account information
/recipients/list
List recipients
/recipients/get/{id}
Get a single recipient
/recipients/new
Create a new recipient
/recipients/delete
Delete a recipient
/recipients/import
Import recipients from a data file
/groups/list
List all groups
/groups/new
Create a new group
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Stannp Direct Mail API by hand means picking between its query API key and basic auth, targeting the EU host, and mapping the recipient, group and import calls yourself. Through Jentic you install once, import the Stannp Direct Mail API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
You limit the agent to the operations it needs, such as listing recipients or getting a recipient by id, so it never runs imports or deletions unless you include them. Because the delete operation takes its target in the request body, scope the agent by operation rather than by a single recipient.
Credential isolation
Your Stannp 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 'get account information' or 'add a mailing recipient', and Jentic returns the matching Stannp Direct Mail API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Stannp Direct Mail API through Jentic.
What authentication does the Stannp Direct Mail API use?
The Stannp Direct Mail API uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get user account information with the Stannp Direct Mail API?
Yes. Use the GET /user/info endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Stannp Direct Mail API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get user account information through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user account information'. Jentic returns the matching Stannp Direct Mail API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Stannp Direct Mail API have?
The Stannp Direct Mail API exposes 29 endpoints covering campaigns, groups, letters operations.
Can I limit what my agent is allowed to do with the Stannp Direct Mail API?
Yes. Because Jentic One is self-hosted, your own rules decide which Stannp operations and credentials the agent may use, so you can allow read calls like GET /recipients/list and GET /recipients/get/{id} while withholding POST /recipients/import and POST /recipients/delete. Since the delete operation takes its target in the request body, you scope the agent by operation rather than by a single recipient. This means an agent can look up recipients without ever running imports or deletions unless you explicitly grant those operations.
For Agents
Programmatically get user account information, list recipients. Covers 29 operations with apiKey, basic authentication.
Use for: I need to user account information, I want to recipients, Search for a single recipient, Find all a new recipient
Not supported: Does not handle payments, communications, or crm - use for marketing only.
API for sending direct mail (postcards, letters), managing recipients, groups, and campaigns through the Stannp platform. The API exposes 29 endpoints secured with apiKey, basic authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>