Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fanaura, 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%2Ffanaura.com%2Ffanaura" | 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%2Ffanaura.com%2Ffanaura" | 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 Fanaura API.
Submit a demo request on behalf of a prospect
Submit a careers application from a person
Read the agent guide and the full question-and-answer text for the site
Read the terms of service and privacy policy as plain text or JSON
Refresh the blog or changelog cache after a content update
GET STARTED
Reach the scoped endpoint for journey and audience data
Patterns agents use Fanaura API for, with concrete tasks.
★ Agent-Readable Marketing Site
A buying agent researching a vendor needs structured facts, not a scraped web page. The Fanaura API serves the agent guide, the full question-and-answer text, the sitemap, and the legal documents as plain text or JSON, so an agent can read what Fanaura offers and cite its terms without parsing HTML.
Read the agent guide and the full question-and-answer text, then read the terms of service as JSON to confirm the usage terms
Demo and Careers Lead Capture
An assistant turns an interested person into a tracked lead. The Fanaura API accepts a demo request or a careers application submitted on a person's behalf, so an agent handling a conversation can file the request directly instead of pointing the person to a web form.
Submit a demo request with the prospect's details through the demo operation and confirm it was accepted
AI Agent Site Access via Jentic
An AI agent reads Fanaura content and files requests through Jentic without handling any credential itself. It searches by intent, receives the matching operation and its input schema, and runs public reads and authenticated submissions with credentials injected at run time where needed, so research and lead capture happen in one flow.
Search Jentic for 'read the Fanaura agent guide', load the operation schema, and fetch the guide with Jentic-managed access
12 endpoints — the fanaura api exposes the fanaura.
METHOD
PATH
DESCRIPTION
/llms.txt
Read the agent guide
/llms-full.txt
Read the full question and answer text
/sitemap.xml
Read the XML sitemap
/api/demo
Submit a demo request
/api/careers
Submit a careers application
/api/revalidate
Refresh the blog or changelog cache
/api/legal/terms
Read the terms of service as JSON
/llms.txt
Read the agent guide
/llms-full.txt
Read the full question and answer text
/sitemap.xml
Read the XML sitemap
/api/demo
Submit a demo request
/api/careers
Submit a careers application
/api/revalidate
Refresh the blog or changelog cache
/api/legal/terms
Read the terms of service as JSON
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Fanaura by hand means handling two different credentials for the protected operations, a shared secret for the content refresh and an OAuth token for the journey endpoint, while leaving the public reads open. Through Jentic you install once, import Fanaura from the API Directory, store any credential once, and your agent calls it.
Permission scoping
Most Fanaura operations are public reads, and the credentialed ones are the content-cache refresh and the journey-and-audience endpoint. A rule can allow the agent to read content and submit demo or careers requests while leaving those two operations out unless you add them.
Credential isolation
Any Fanaura credential, the refresh secret or the OAuth 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 'read the Fanaura agent guide' or 'submit a demo request', and Jentic returns the matching Fanaura 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 Fanaura API through Jentic.
What authentication does the Fanaura API use?
Most of the Fanaura API is public and needs no credential: reading the agent guide, sitemap, and legal pages, and submitting demo or careers requests are public operations. Two operations take a credential per the spec: refreshing the content cache uses a shared secret in the x-revalidate-secret header, and the journey-and-audience endpoint uses an OAuth 2.0 access token. Through Jentic any credential is stored encrypted by your own Jentic One instance and injected at execution time.
Can I submit a demo request with the Fanaura API?
Yes. The demo operation accepts a demo request submitted on a person's behalf, and the careers operation does the same for job applications. Both are public operations, so an agent can file a request straight from a conversation without routing the person to a web form.
What are the rate limits for the Fanaura API?
The OpenAPI spec does not specify rate limits for the Fanaura API. Check the Fanaura documentation for current limits, and note that public content endpoints can be requested with an Accept header of text/markdown when you want Markdown rather than HTML.
How do I read Fanaura's site content with the Fanaura API through Jentic?
Search Jentic for 'read the Fanaura agent guide' and it returns the matching operation with its input schema. Load the schema and fetch the guide or the question-and-answer text, with any credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Fanaura API?
Yes. Most operations are public reads, and for the credentialed ones you choose which the agent may call. Allow the content reads and the demo and careers submissions while leaving the content-cache refresh and the journey-and-audience endpoint out unless you add them, and every call runs through your own instance where it is logged.
Is there a Fanaura MCP server?
Yes, Fanaura runs an MCP server reached through its /mcp endpoint, with OAuth scopes for journeys and audience. You can also connect Fanaura directly through Jentic: your agent gets the published HTTP operations without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.
For Agents
Read Fanaura's published site content and legal documents, submit demo and careers requests, refresh the content cache, and reach a scoped journey-and-audience endpoint. Most operations are public; two take a credential.
Use for: Read the agent guide for Fanaura, Get the full question and answer text for the site, Submit a demo request for a prospect, Submit a careers application
Not supported: Does not handle payments, email campaigns, or analytics dashboards. Use for reading Fanaura's published site content and capturing demo and careers requests only.
The Fanaura API exposes the fanaura.com site to agents and captures inbound interest. Agents can read the published agent guide, the full question-and-answer text, the XML sitemap, and the terms and privacy policy as plain text or JSON. People-facing operations submit a demo request or a careers application, a content-refresh operation updates the blog or changelog cache, and a scoped endpoint serves journey and audience data. Public pages can be requested as Markdown.
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>