ainative-api-discoveryHelp agents discover and navigate AINative's 89+ API endpoints. Use when (1) Asking "what endpoints exist?", (2) Finding the right API for a task, (3) Lookin...
Install via ClawdBot CLI:
clawdbot install urbantech/ainative-api-discoveryGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://api.ainative.studio/v1/public/chat/completionsCalls external URL not in known-safe list
https://api.ainative.studio`.AI Analysis
The skill is a static API reference document that describes endpoints for the AINative platform. It does not contain executable code, instructions to send data, or any hidden logic that could exfiltrate information or override user intent. The 'external calls' flagged are merely documented endpoint URLs, not actions the skill performs.
Audited Apr 16, 2026 · audit v1.0
Generated Sep 30, 2026
A startup needs to quickly add chat completions, API key management, and model listing to their SaaS product without building backend AI infrastructure. They use the AINative discovery skill to locate the correct chat and authentication endpoints, then copy the Python code example to get a working integration in hours instead of weeks. This accelerates their MVP launch while maintaining a clean REST API architecture.
A fintech support team wants their AI assistant to remember past customer interactions and surface relevant context during live chats. They use the ZeroMemory endpoints for remember, recall, and profile retrieval to build a persistent memory layer that personalizes responses. The semantic recall endpoint lets them search millions of past conversations instantly without managing vector databases themselves.
An indie developer builds a public directory of AI-powered tools and monetizes through the Echo developer program. They integrate registration, earnings tracking, and markup configuration endpoints to let contributors set their own rates and receive payouts. The billing and credits endpoints give them real-time insight into usage revenue and subscription conversions.
A healthcare SaaS company needs semantic document search across patient education materials while keeping data isolated in HIPAA-compliant storage. They use ZeroDB vector upsert and search endpoints to embed and retrieve documents, combined with file upload for ingesting PDFs. This provides enterprise-grade retrieval-augmented generation without maintaining separate Pinecone or Weaviate infrastructure.
A company building an AI wrapper product needs to track and display per-user credit consumption, manage subscription plans, and issue invoices. They query the credits balance and usage history endpoints, then connect billing subscription and invoice endpoints to a customer portal. This enables transparent usage-based pricing directly from the AINative API without a separate billing microservice.
Developers register through the Echo program, build applications on AINative endpoints, and resell AI capabilities to their own customers with a configurable markup of 0-40%. Revenue is generated from the spread between AINative's base cost and the end-user price, tracked via earnings and payout endpoints. This model turns the API into a white-label AI platform for indie builders.
Businesses subscribe customers to monthly plans and pre-purchase credit buckets consumed by chat, memory, and vector operations. Credits are monitored through the balance and usage endpoints, while billing subscribe and invoices endpoints handle recurring charges. This creates predictable recurring revenue with clear upgrade paths when users exhaust their credit allowance.
A vertical SaaS product differentiates itself by offering persistent AI memory and knowledge graphs on top of standard chat completions. The ZeroMemory and ZeroDB endpoints form the technical moat, allowing users to accumulate personal or organizational context that increases switching costs. This enables premium pricing versus commodity chatbot competitors.
💬 Integration Tip
Start with the Python or curl chat completion example to validate your API key, then explore the memory, credits, and ZeroDB categories as your features grow; always store API keys in environment variables and use the /health endpoint to confirm connectivity before adding endpoints to production.
Scored Sep 30, 2026
API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user...
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
API Design Reviewer
Cut AI token costs by 60-85% with deterministic query validation and intelligent caching. Standalone or integrates with Company Brain Core OS. Free, open-sou...
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Ann...