canonical: https://jentic.com/apis/fanaura.com/fanaura # Fanaura 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. ## For AI 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. ## Scope Does not handle payments, email campaigns, or analytics dashboards. Use for reading Fanaura's published site content and capturing demo and careers requests only. ## Capabilities - 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 - Reach the scoped endpoint for journey and audience data ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'read the Fanaura agent guide', load the operation schema, and fetch the guide with Jentic-managed access ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/llms.txt` | Read the agent guide | | GET | `/llms-full.txt` | Read the full question and answer text | | GET | `/sitemap.xml` | Read the XML sitemap | | POST | `/api/demo` | Submit a demo request | | POST | `/api/careers` | Submit a careers application | | POST | `/api/revalidate` | Refresh the blog or changelog cache | | GET | `/api/legal/terms` | Read the terms of service as JSON | ## Key resources - **Published Content** — Read agent-facing content via /llms.txt, /llms-full.txt, and /sitemap.xml - **Legal** — Read terms and privacy as text or JSON via /privacy-policy.txt, `/api/legal/terms`, and `/api/legal/privacy` - **Submissions and Cache** — Capture requests and refresh content via `/api/demo`, `/api/careers`, and `/api/revalidate` ## AI readiness 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. - **Score:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 59 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 70 / 100 - AI Discoverability: 70 / 100 - **View full report:** https://jentic.com/apis/fanaura.com/fanaura/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Klaviyo API** — Marketing automation with audiences, journeys, and campaigns - **Mailchimp Marketing API** — Email marketing and audience management - **Typeform API** — Build forms and collect richer structured responses ## FAQ ### 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.