Use the supported integration surfaces clearly
Tusula exposes focused integration points rather than claiming a general public API that is not yet available.
AI crawl ingestion
Create a project ingestion key in Crawl Monitor and send normalized crawler events to the public crawl-events endpoint.
X-Tusula-Crawl-Key header
User agent, path, status, bytes and timestamp
Server or CDN log forwarding
Website chatbot embed
Generate the project widget script from Website Chatbot and place it once on an allowed website domain.
Allowed-origin validation
Per-visitor consent and rate limits
Verified answers and optional lead capture
OAuth integrations
Google, LinkedIn and X use official authorization callbacks and encrypted project-bound tokens.
Search Console and Analytics read access
LinkedIn and X publishing permissions
Explicit connect and disconnect controls
Bing, IndexNow and Commerce
Bing Webmaster uses an encrypted project API key. IndexNow requires a key file that your team places on the site. Commerce can synchronize a public XML, CSV or JSON feed URL.
Verified Bing property selection
Changed-URL submission only after manual updates
Recurring catalog synchronization
AI revenue tracking
Install the project base snippet after analytics consent and send a purchase or lead-success event from your confirmed conversion flow.
Supported AI-referral recognition
Hashed conversion ID deduplication
No raw order ID or personal metadata storage
Workspace API keys
Create named, expiring keys and revoke them from account settings. Treat them as sensitive even while the broader key-authenticated API surface is limited.
Secret shown only once
Optional company scope and expiry
Immediate revocation from settings