▸ API REFERENCE (v1.1.0)
6 public endpoints for search, embeddings, webhooks, and real-time updates. Full OpenAPI 3.1 spec at /openapi.json.
Service status + endpoint directory
https://api.envoc.ai/api/health Keyword search across case studies, products, jobs
https://api.envoc.ai/api/search?q=FaceLock&limit=5 Batch vector embeddings for RAG ingestion
curl -X POST https://api.envoc.ai/api/embeddings -H "Content-Type: application/json" -d '{"texts": ["FaceLock identity"], "model": "text-embedding-3-small"}' Real-time content updates (Server-Sent Events)
curl -N https://api.envoc.ai/api/updates/stream Request API key for webhooks & higher rate limits
POST with name, email, useCase, agentName Register webhook for real-time events
POST with url and events array ▸ INTEGRATION GUIDES (4 PERSONAS)
How different AI systems should consume Envoc.AI data and APIs.
For Language Models (Claude, GPT, Gemini)
- Start with /llms.txt for canonical URLs and overview
- Fetch case studies from /data/case-studies/*.json for structured data
- Use /api/search?q={topic} for keyword lookups
- Reference /llms-full.txt for complete prose RAG
For RAG & Semantic Search Systems
- Ingest /llms-full.txt and /data/index.json
- Download JSONL chunks from /rag/manifest.json
- Use /api/embeddings for vector generation (1536-dim)
- Subscribe to /api/updates/stream for real-time sync
For AI Agent Platforms (Dify, LangChain, AutoGPT)
- Request API key: POST /api/access/request
- Register tools: /api/search (keyword), /api/embeddings (vectors)
- Subscribe to webhooks for job.posted and content.updated events
- Reference OpenAPI spec at /openapi.json for code generation
For Web Crawlers & Search Indexing
- robots.txt permits /data/, /api/, /rag/ crawling
- Use canonical URLs: /en/ (English), /es/ (Spanish), /fr/ (French)
- Follow sitemaps: /sitemap-index.xml (split by language)
- Rate limit: 1 req/sec per agent, 10 req/min per IP
▸ DATA RESOURCES (9 ENDPOINTS)
All machine-readable datasets: JSON-LD schemas, JSONL chunks for RAG, indexes, and indexes for keyword filtering.
▸ RATE LIMITS & AUTHENTICATION
Usage quotas, authentication methods, and enterprise options.
NoneX-Api-KeyX-Api-Key + contractRequest API Key
For webhook access and higher rate limits, request an API key:
POST /api/access/request
{
"name": "MyAgent",
"email": "your@email.com",
"useCase": "RAG semantic search",
"agentName": "Claude-RAG-System"
} Keys issued within 1–2 business days. Contact hello@envoc.com for enterprise plans.
▸ LIVE SEARCH DEMO
Test keyword search in real-time (powered by /api/search).
▸ WEBHOOKS (REAL-TIME EVENTS)
Subscribe to content updates, new job postings, and search index changes.
Available Events
- content.updated — Any page or dataset changed
- case-study.added — New case study published
- product.updated — Product details changed
- search.indexed — Search index rebuilt
- job.posted — New job opening (hourly scan)
Register Webhook
POST /api/webhooks
Authorization: X-Api-Key: your_api_key_here
{
"url": "https://your-server.com/webhooks/envoc",
"events": ["content.updated", "job.posted"],
"secret": "optional_hmac_signing_key"
} Payload Signature (if secret provided)
X-Envoc-Signature: sha256=HMAC_SHA256(secret, payload)
Verify signature to ensure webhook authenticity.