etherFAX

etherFAX provides secure, cloud-based faxing solutions powered by AI-driven document workflows. Serving government, commercial, and healthcare sectors, it offers FedRAMP-certified and HIPAA-compliant services. The platform enables sending and receiving faxes directly from desktop applications, integrating with various enterprise systems, and automating document exchange processes.

etherFAX publishes 6 API contracts indexed on the APIs.io network, including Accounts API, Devices API, Inbox API, and 3 more. Tagged areas include Fax, Cloud, Artificial Intelligence, Secure, and Document Automation.

The etherFAX catalog on APIs.io includes 1 Spectral governance ruleset.

etherFAX’s developer surface includes authentication, documentation, engineering blog, support, and 21 more developer resources.

41.7/100 developing ▬ flat Agent 35/100 agent ready Full breakdown ↓
scored 2026-11-01 · rubric v0.26.0 · Show this score on your site →
1 published contract 1 Agent Skills
FaxCloudArtificial IntelligenceSecureDocument Automation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-01 · rubric v0.26.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for etherFAX It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/etherfax/"><img src="https://apis.io/badge/etherfax/card.svg" alt="etherFAX on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/etherfax/apis.yml: open an issue on github.com/api-evangelist/etherfax to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

etherFAX Accounts API

The Accounts API from etherFAX — 2 operation(s) for accounts.

etherFAX Devices API

The Devices API from etherFAX — 8 operation(s) for devices.

etherFAX Inbox API

The Inbox API from etherFAX — 5 operation(s) for inbox.

etherFAX Outbox API

The Outbox API from etherFAX — 1 operation(s) for outbox.

etherFAX Routes API

The Routes API from etherFAX — 4 operation(s) for routes.

etherFAX Status API

The Status API from etherFAX — 1 operation(s) for status.

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

etherFAX API Rules

12 rules · 10 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Etherfax Openapi Overlay

0 actions · update

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Etherfax Authentication

http · 1 scheme

SECURITY

Etherfax Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Etherfax Trust Center

PCI DSS, HIPAA, FedRAMP, GDPR

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Etherfax Agentic Access

23 operations · 4 acting

23 operations · 4 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 6

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: etherfax
name: etherFAX
image: https://www.etherfax.net/wp-content/uploads/2026/06/EF-HomePageRefresh26-FeaturedImage2.webp
description: etherFAX provides secure, cloud-based faxing solutions powered by AI-driven document workflows. Serving government,
  commercial, and healthcare sectors, it offers FedRAMP-certified and HIPAA-compliant services. The platform enables sending
  and receiving faxes directly from desktop applications, integrating with various enterprise systems, and automating document
  exchange processes.
url: https://raw.githubusercontent.com/api-evangelist/etherfax/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-27 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-26'
modified: '2026-10-26'
tags:
- Fax
- Cloud
- Artificial Intelligence
- Secure
- Document Automation
tags_raw:
- Fax
- Cloud
- AI
- Secure
- DocumentAutomation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/etherfax-agentic-access.yml
- type: Spectral
  url: rules/etherfax-rules.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Compliance
  url: https://www.etherfax.net/security/
- type: ErrorCatalog
  url: errors/etherfax-problem-types.yml
- type: Conformance
  url: conformance/etherfax-conformance.yml
- type: LLMsTxt
  url: llms/etherfax-llms.txt
- type: SecurityTxt
  url: well-known/etherfax-status-security.txt
- type: WellKnown
  url: well-known/etherfax-well-known.yml
- type: Hosts
  url: hosts/etherfax-hosts.yml
- type: Vendors
  url: vendors/etherfax-vendors.yml
- type: TermsOfService
  url: https://www.etherfax.net/terms-conditions/
- type: StatusPage
  url: https://status.etherfax.net/
- type: Security
  url: https://www.etherfax.net/security/
- type: Newsroom
  url: https://www.etherfax.net/news/
- type: Login
  url: https://www.etherfax.net/login/
- type: Leadership
  url: https://www.etherfax.net/about/team/
- type: Authentication
  url: authentication/etherfax-authentication.yml
- type: TrustCenter
  url: security/etherfax-trust-center.yml
- type: DomainSecurity
  url: security/etherfax-domain-security.yml
- type: Website
  url: https://www.etherfax.net/
- type: DeveloperPortal
  url: https://www.etherfax.net/developer-apis/
- type: Documentation
  url: https://docs.etherfax.net/
- type: Blog
  url: https://www.etherfax.net/blogs/
- type: Support
  url: https://www.etherfax.net/support/
apis:
- aid: etherfax:etherfax-accounts-api
  name: etherFAX Accounts API
  description: The Accounts API from etherFAX — 2 operation(s) for accounts.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/etherfax-accounts-api-openapi.yml
- aid: etherfax:etherfax-devices-api
  name: etherFAX Devices API
  description: The Devices API from etherFAX — 8 operation(s) for devices.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/etherfax-devices-api-openapi.yml
- aid: etherfax:etherfax-inbox-api
  name: etherFAX Inbox API
  description: The Inbox API from etherFAX — 5 operation(s) for inbox.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Inbox
  properties:
  - type: OpenAPI
    url: openapi/etherfax-inbox-api-openapi.yml
- aid: etherfax:etherfax-outbox-api
  name: etherFAX Outbox API
  description: The Outbox API from etherFAX — 1 operation(s) for outbox.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Outbox
  properties:
  - type: OpenAPI
    url: openapi/etherfax-outbox-api-openapi.yml
- aid: etherfax:etherfax-routes-api
  name: etherFAX Routes API
  description: The Routes API from etherFAX — 4 operation(s) for routes.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Routes
  properties:
  - type: OpenAPI
    url: openapi/etherfax-routes-api-openapi.yml
- aid: etherfax:etherfax-status-api
  name: etherFAX Status API
  description: The Status API from etherFAX — 1 operation(s) for status.
  baseURL: https://na.connect.etherfax.net/rest/3.0/api
  tags:
  - Status
  properties:
  - type: OpenAPI
    url: openapi/etherfax-status-api-openapi.yml
x-submission-probe: 301 (-> https://www.etherfax.net) 2026-10-25
x-coverage:
  state: unreadable
  reason: js-rendered-docs
  detail: Documentation site renders OpenAPI spec behind a JavaScript app, preventing machine-readable retrieval.
  evidence:
  - url: https://docs.etherfax.net/openapi.json
    status: 200
  checked: '2026-10-27'
x-enrichment:
  date: '2026-10-27'
  status: enriched
  artifacts_added: 22
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

etherFAX API — frequently asked questions

Does etherFAX have an API?

Yes. APIs.io lists 6 APIs from etherFAX, including etherFAX Accounts API, etherFAX Devices API and etherFAX Inbox API, and 3 more.

Is there an OpenAPI specification for the etherFAX API?

Yes. APIs.io indexes 6 OpenAPI specifications for etherFAX, each linked for download from this page.

How do I authenticate with the etherFAX API?

etherFAX documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Etherfax Authentication.

Is the etherFAX API ready for AI agents?

etherFAX has a Kin Score of 41.7 out of 100 (developing) and an Agent Readiness score of 34.9 (agent-ready), scored by API Evangelist on 2026-11-01.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/etherfax"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/etherfax/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/etherfax/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.