For Agents
Send a one-recipient PDF fax to US and Canada numbers: upload the PDF, get an exact quote, charge the prepaid balance to send, and track delivery state and records.
Use for: Get a price quote for faxing a PDF, Upload a PDF and create a fax draft with a quote, Send a fax to a US number and charge my balance, Check my available prepaid fax balance
Not supported: Does not send email, SMS, or voice calls, and does not reach destinations outside the US and Canada. Use for outbound PDF fax only.
The Edwyna API sends paid outbound faxes to United States and Canada destinations, powered by FaxZero. An agent uploads one PDF of up to 25 pages, creates a draft that synchronously validates the document and returns an exact server-generated quote, then sends the fax to a single recipient by charging the prepaid balance. It also reports authoritative pricing, the available balance, each fax's delivery state, and downloadable transmitted-document and delivery-record PDFs.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Edwyna 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%2Fedwyna.com%2Fedwyna" | 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%2Fedwyna.com%2Fedwyna" | 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 Edwyna API.
Upload a PDF and get an exact server-generated fax quote before sending
Send a one-recipient fax to US and Canada destinations by charging the prepaid balance
Check the available prepaid balance and authoritative per-fax pricing
List faxes and read each fax's current delivery state
Download the transmitted document and the delivery-record PDF after delivery
Patterns agents use Edwyna API for, with concrete tasks.
★ Agent-sent document fax
An agent that needs to fax a signed document uploads the PDF to Edwyna, creates a draft to validate it and receive an exact quote, then sends it to the recipient by charging the prepaid balance. The upload, draft, and send operations are discovered through Jentic by intent, so the agent runs the sequence without wiring the handoff steps by hand.
Upload a PDF, create a fax draft to get the quote, then send the fax to one recipient and confirm it was queued
Pre-send quoting and balance checks
Before committing to a send, an agent reads Edwyna's authoritative pricing and the available prepaid balance to confirm there is enough credit to cover the quote. Creating a draft is non-consequential and does not deduct credit, so the agent can validate and price a fax without sending it.
Fetch the fax price and the current prepaid balance, then create a draft to confirm the exact quote without sending
Delivery tracking and record retrieval
After a fax is sent, an agent polls its delivery state and, once delivered, downloads the transmitted document and Edwyna's delivery-record PDF for an audit trail. This lets a workflow confirm receipt and archive proof of transmission for each fax.
Check a fax's delivery state, and once it is delivered, download its delivery-record PDF
10 endpoints — the edwyna api sends paid outbound faxes to united states and canada destinations, powered by faxzero.
METHOD
PATH
DESCRIPTION
/v1/fax-drafts
Upload, validate, and quote one PDF fax
/v1/fax-drafts/{fax_id}/send
Charge the prepaid balance and queue one fax
/v1/faxes
List faxes for the authenticated customer
/v1/faxes/{fax_id}
Get one fax and its delivery state
/v1/pricing
Get an authoritative fax price
/v1/balance
Get the available prepaid balance
/v1/pdf-uploads
Create a single-use PDF upload URL
/v1/faxes/{fax_id}/delivery-record
Download the delivery-record PDF
/v1/fax-drafts
Upload, validate, and quote one PDF fax
/v1/fax-drafts/{fax_id}/send
Charge the prepaid balance and queue one fax
/v1/faxes
List faxes for the authenticated customer
/v1/faxes/{fax_id}
Get one fax and its delivery state
/v1/pricing
Get an authoritative fax price
/v1/balance
Get the available prepaid balance
/v1/pdf-uploads
Create a single-use PDF upload URL
/v1/faxes/{fax_id}/delivery-record
Download the delivery-record PDF
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Edwyna API by hand means handling its bearer API secret, keeping enough prepaid balance to cover each quote, and sequencing the PDF upload, draft, and send steps yourself. Through Jentic you install once, import the Edwyna API from the API Directory, store the secret once, and your agent calls it.
Permission scoping
Edwyna puts the fax id in the URL path (/v1/faxes/{fax_id}), so a rule can limit your agent to reading and tracking faxes. You choose the operations it may call, so the balance-charging send operation is not included unless you add it.
Credential isolation
Your Edwyna secret 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 'quote a fax' or 'send a PDF fax', and Jentic returns the matching Edwyna 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 Edwyna API through Jentic.
What authentication does the Edwyna API use?
The Edwyna API authenticates with a bearer API secret per its OpenAPI spec, and each key carries explicit scopes and spending limits. Through Jentic the secret is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context or a user-visible prompt.
Can I send a fax to a US number with the Edwyna API?
Yes. Edwyna sends one PDF of up to 25 pages to a single recipient at US and Canada destinations. You upload the PDF, create a draft to validate it and get an exact quote, then call the send operation to charge your prepaid balance and queue the fax.
What are the rate limits for the Edwyna API?
The OpenAPI spec does not state request rate limits; sending is gated by your available prepaid balance, which must cover the quote. Check the Edwyna documentation at https://edwyna.com for current limits and pricing.
Is there an Edwyna MCP server?
You don't need an MCP server to give your agent the Edwyna API. Jentic connects it directly from the API Directory: import it, store your secret once, and your agent calls the quote, send, and tracking operations it needs.
Can I limit what my agent is allowed to do with the Edwyna API?
Yes. Write a rule that allows only the read operations, such as pricing, balance, and fax status, so the agent can quote and track faxes but cannot spend your balance. The balance-charging send operation is left out unless you add it, and every call the agent makes is logged.
How do I send a fax through Jentic?
Search Jentic for 'send a PDF fax', and it returns the Edwyna draft and send operations with their input schemas; your agent uploads the PDF, confirms the quote, and sends. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED