Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer11 EndpointsREST
For Agents
Programmatically get current user, create lists. Covers 11 operations with bearer authentication.
Use for: I need to current user, I want to lists, Search for lists, Find all lists
Not supported: Does not handle payments, communications, or crm - use for marketing only.
SendFox email marketing API. The API exposes 11 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the SendFox API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendFox 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.
1
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%2Fsendfox.com%2Fsendfox" | sh2
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%2Fsendfox.com%2Fsendfox" | 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.
Capabilities
What an agent can do with SendFox API.
Get current user
Create Lists
List Lists
Query and filter SendFox API records by parameters
Monitor SendFox API operational status and events
Use Cases
Patterns agents use SendFox API for, with concrete tasks.
★ Marketing Operations
Use the SendFox API to perform marketing operations programmatically. The API provides 11 endpoints covering core functionality including get current user, create lists, list lists.
Call GET /me to get current user
Automated Campaigns Management
Automate campaigns operations by combining multiple SendFox API endpoints. Agents can create lists and then list lists in a single workflow.
Call POST /lists to create lists, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SendFox 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 bearer tokens manually.
Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
11 endpoints — sendfox email marketing api.
METHOD
PATH
DESCRIPTION
GET
/me
Get current user
POST
/lists
Create Lists
GET
/lists
List Lists
GET
/lists/{id}
Get Lists
POST
/contacts
Create Contacts
GET
/contacts
List Contacts
GET
/contacts/{id}
Get Contacts
POST
/contacts/{id}/unsubscribe
Unsubscribe contact
GET
/me
Get current user
POST
/lists
Create Lists
GET
/lists
List Lists
GET
/lists/{id}
Get Lists
POST
/contacts
Create Contacts
GET
/contacts
List Contacts
GET
/contacts/{id}
Get Contacts
POST
/contacts/{id}/unsubscribe
Unsubscribe contact
Jentic AI Readiness Score
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.
S
SendFox API
- Foundational (C+)57/100
75
Foundational Compliance56
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience94
Agent Usability60
Security55
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
75
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
2%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
17%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
82%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
55
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
55%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SendFox API by hand means learning its bearer auth, calling api.sendfox.com, and managing list and contact payloads yourself. Through Jentic you install once, import the SendFox API from the API Directory, store the token once, and your agent calls it.
Permission scoping
SendFox puts the list and contact ids in the URL path (/lists/{id}, /contacts/{id}), so a rule can pin your agent to reading one list. You choose the operations it may call, so contact unsubscription is not included unless you add it.
Credential isolation
Your SendFox 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 'get the current user' or 'add a contact to a list', and Jentic returns the matching SendFox API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SendFox API through Jentic.
What authentication does the SendFox API use?
The SendFox API uses a Bearer token in the Authorization header. 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 current user with the SendFox API?
Yes. Use the GET /me endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SendFox 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 current user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching SendFox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SendFox API have?
The SendFox API exposes 11 endpoints covering campaigns, contacts, lists operations.
Can I limit what my agent is allowed to do with the SendFox API?
Yes. Because you run Jentic One yourself, your own rules decide which SendFox operations and credentials the agent may use, so you can grant read-only access to lists and contacts (GET /lists, GET /lists/{id}, GET /contacts) while withholding writes like POST /contacts or POST /contacts/{id}/unsubscribe. Since SendFox puts the list and contact ids in the URL path, a rule can pin the agent to a single list or contact rather than the whole account. The agent can only call the operations you have explicitly allowed.
GET STARTED