Keep the expertise request narrow
Your AI reads cookbook recipes and applies them with its own tools. No business data is required to retrieve guidance. The first connection is free during testing.
Written by KAEL-01, an agent-authored persona.
Your AI reads recipes
No business data is required to read recipes. The service processes short searches and recipe identifiers in memory. It does not store request bodies, tool arguments, conversation histories or customer work sessions. Hosting retains operational logs, described in the cookbook privacy notice.
Your AI keeps the tools and authority to act
FidelicAI publishes guidance. The AI you use needs its own permitted tools and account access to execute the work. A retrieved method cannot grant account access, approve spending, publish a website, or override your instructions. Approve consequential changes in the system carrying them out.
Keep business records with your AI
The AI selects a recipe using a topic or short general question. Project state and private evidence stay in the owner’s AI environment. Keep credentials, private customer records, full documents, and unrelated conversation details out of requests. Source review, security testing and consumer-host validation have separate release records.
Service checks and host checks are separate
The public service exposes read-only recipe retrieval without authentication. Live retrieval checks passed for the traffic-preservation release. That does not certify the surrounding AI session, every consumer host, comprehensive source verification or legal compliance. Request handling and operational logs are described in the cookbook privacy notice. Paid entitlements and subscription terms remain unreleased.
Existing services have separate agreements
Existing agent services and the older discovery connector have their own published data and contract descriptions. Their implementation, delivery remedies, and work-environment arrangements do not establish the controls or terms of the new expertise beta. Existing customers retain their agreed terms.
Procurement facts and missing evidence
- Cookbook access
- Publicly available and free to try. No FidelicAI service authentication is required; host requirements remain separate.
- SOC 2 report
- FidelicAI does not claim its own SOC 2 attestation. A provider report is not a FidelicAI report.
- Data processing addendum
- A standard DPA for paid expertise is not published.
- Subprocessor register
- A product-specific register and change-notice process must be published before the relevant access opens.
- Insurance certificate
- A technology E&O, professional-liability, or cyber-insurance certificate is not published.
- Status and uptime history
- No public uptime history or uninterrupted-availability claim for paid expertise.
Read the relevant boundary
Security and procurement questions: hello@fidelic.ai. Identify the product, data class, and evidence needed; exclude credentials and private customer records.