Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Phaxio Fax 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%2Fphaxio.com%2Fphaxio" | 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%2Fphaxio.com%2Fphaxio" | 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 Phaxio Fax API.
Send faxes to one or multiple recipients with file attachments or content URLs
Receive inbound faxes on provisioned phone numbers with webhook notifications
Provision and release dedicated fax phone numbers across US and Canadian area codes
Retrieve sent and received fax content as PDF files
Track fax delivery status including page count, duration, and error details
GET STARTED
Look up available area codes for fax number provisioning by state or region
Monitor account usage including pages sent, pages received, and current balance
Patterns agents use Phaxio Fax API for, with concrete tasks.
★ Automated Document Faxing
Send documents via fax to recipients who require fax-based delivery, such as healthcare providers, legal offices, and government agencies. Phaxio handles the phone line connection, retry logic, and delivery confirmation automatically. Supports batch sending to multiple recipients in a single API call with individual delivery tracking per recipient.
Send a fax to +1-555-0100 with a PDF file attachment and confirm delivery status within 5 minutes
Inbound Fax Reception
Receive faxes on dedicated phone numbers and process them programmatically. Phaxio provisions local or toll-free numbers, receives incoming faxes, and delivers the content as downloadable files via webhook notification. Useful for digitizing fax workflows in healthcare, legal, and insurance industries where counterparties still rely on fax communication.
Provision a new fax number in area code 212 and configure a webhook URL to receive inbound fax notifications
Fax Number Management
Provision, manage, and release dedicated fax phone numbers across US and Canadian area codes. Look up available area codes by region, assign numbers for specific departments or use cases, and release numbers when no longer needed. Each number supports both sending and receiving faxes.
List all available area codes in New York state and provision a fax number from the 718 area code
AI Agent Fax Integration via Jentic
AI agents can send and track faxes through Jentic without managing Phaxio credentials directly. An agent searches for fax-sending operations, loads the endpoint schema, and executes the call with Jentic handling authentication. This enables agents to fulfill requests like sending legal documents or healthcare forms via fax as part of a larger automated workflow.
Search Jentic for 'send a fax with PDF attachment', load the Phaxio send fax operation schema, and execute the call to fax a document to +1-555-0199
13 endpoints — jentic publishes the only available openapi specification for phaxio fax api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/faxes
Send a fax to one or more recipients
/faxes
List faxes with filters for date range and status
/faxes/{id}
Get detailed status of a specific fax
/faxes/{id}/file
Download fax content as PDF
/faxes/{id}/cancel
Cancel a queued fax
/faxes/{id}/resend
Resend a previously sent fax
/phone_numbers
List provisioned fax phone numbers
/public/area_codes
Look up available area codes for provisioning
/faxes
Send a fax to one or more recipients
/faxes
List faxes with filters for date range and status
/faxes/{id}
Get detailed status of a specific fax
/faxes/{id}/file
Download fax content as PDF
/faxes/{id}/cancel
Cancel a queued fax
/faxes/{id}/resend
Resend a previously sent fax
/phone_numbers
List provisioned fax phone numbers
/public/area_codes
Look up available area codes for provisioning
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Phaxio Fax API by hand means setting up its basic auth with your API key as the username and secret as the password on api.phaxio.com/v2.1, then formatting the fax send and status requests yourself. Through Jentic you install once, import the Phaxio Fax API from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
Phaxio puts the fax id in the URL path (/faxes/{id}), so a rule can pin your agent to one fax: it can read that fax, fetch its file, cancel or resend it. You choose the operations it may call, so send or cancel are not included unless you add them.
Credential isolation
Your Phaxio API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a fax' or 'check fax delivery status', and Jentic returns the matching Phaxio 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 Phaxio Fax API through Jentic.
Why is there no official OpenAPI spec for Phaxio Fax API?
Phaxio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Phaxio Fax API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Phaxio Fax API use?
Phaxio uses HTTP Basic authentication. Your API key serves as the username and your API secret serves as the password. Through Jentic, these credentials are stored encrypted in your Jentic One instance, so agents never handle raw secrets directly.
Can I send a fax to multiple recipients with the Phaxio API?
Yes. The POST /faxes endpoint accepts multiple recipient phone numbers in a single request. Each recipient gets an individual delivery status that you can track via GET /faxes/{id}. Supported file formats include PDF, DOC, DOCX, and plain text.
What are the rate limits for the Phaxio Fax API?
Phaxio rate limits are tied to your account plan. The API returns HTTP 429 when limits are exceeded. Fax delivery itself is constrained by phone line capacity rather than API rate limits, so large batch sends are queued and processed sequentially per recipient number.
How do I retrieve a received fax as a PDF through Jentic?
Search Jentic for 'download fax content' to find the GET /faxes/{id}/file operation. Load the schema, provide the fax ID from your inbound webhook payload, and execute the call. Jentic returns the PDF binary content with the correct content-type header.
Which area codes can I provision fax numbers in?
Use GET /public/area_codes to retrieve the full list of available area codes. You can filter by state or country. Phaxio supports US and Canadian area codes including local and toll-free numbers. Provisioning is immediate once you select an available number.
Can I limit what my agent is allowed to do with the Phaxio Fax API?
Yes. Because you run Jentic One yourself, your own rules decide which Phaxio operations and credentials your agent may use. Phaxio puts the fax id in the URL path (/faxes/{id}), so you can pin the agent to a single fax and let it only read that fax, download its file (GET /faxes/{id}/file), cancel it, or resend it. You pick the exact operations it can call, so sending a new fax (POST /faxes) or provisioning a phone number stays off limits unless you grant it. Your API key and secret are held by your own instance and injected only at execution, never exposed to the agent.
Know of an official OpenAPI document? Contribute it →
For Agents
Send and receive faxes programmatically, provision phone numbers, retrieve fax content, and look up available area codes for fax number assignment.
Use for: I need to send a fax to a phone number with a PDF attachment, I want to provision a new fax phone number in a specific area code, Check whether a fax was successfully delivered, List all faxes sent in the last 24 hours
Not supported: Does not handle email, SMS, voice calls, or document signing - use for fax transmission and phone number provisioning only.
Jentic publishes the only available OpenAPI specification for Phaxio Fax API, keeping it validated and agent-ready. Phaxio provides a programmatic interface for sending and receiving faxes, provisioning phone numbers, and managing fax content. The API supports batch fax delivery, fax status tracking, phone number management across US and Canadian area codes, and account-level reporting with 13 endpoints covering the full fax lifecycle.
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>