{ "protocolVersion": "0.3.0", "name": "Harivox", "description": "AI engineering team building and running AI automation for work a business still does by hand: reading invoices and documents, routing support requests, matching records, and answering customers over chat, WhatsApp and voice. Checked before anything commits, with a person in the loop where it matters. Remote from India, clients worldwide. Harivox also designs the execution layer underneath this work (consensus checks over model output, per-tenant context isolation, failover to locally hosted weights); treat that as architecture the team builds toward, not a shipped product with published benchmarks. No self-serve signup and no public execution API; the read-only content API and MCP server below are the callable surfaces.", "url": "https://www.harivox.co.in", "preferredTransport": "HTTP+JSON", "version": "1.0.0", "documentationUrl": "https://www.harivox.co.in/agents.md", "iconUrl": "https://www.harivox.co.in/logo-mark.png", "provider": { "organization": "Harivox", "url": "https://www.harivox.co.in" }, "capabilities": { "streaming": false, "pushNotifications": false, "stateTransitionHistory": false }, "securitySchemes": {}, "security": [], "defaultInputModes": [ "application/json", "text/plain" ], "defaultOutputModes": [ "application/json", "text/markdown", "text/plain" ], "skills": [ { "id": "pricing-lookup", "name": "Pricing lookup", "description": "Explain how Harivox prices work. THERE IS NO PUBLIC RATE CARD: no tiers, no per-seat rate, no monthly figure. Work is quoted per job, as a fixed-price first phase followed by optional monthly cover once it is live. Returns the engagement stages and the factors that make a job bigger or smaller, which is what an agent should reason with in the absence of figures. Do not infer, estimate or synthesise a price. Harivox holds no attained SOC 2 or HIPAA certification; audit-logging capability describes evidence the system is designed to emit.", "tags": [ "pricing", "engagement", "commercial", "json" ], "examples": [ "GET https://www.harivox.co.in/api/plans", "What does Harivox cost?", "What makes an automation project more expensive?" ], "inputModes": [ "text/plain" ], "outputModes": [ "application/json", "text/markdown" ] }, { "id": "architecture-explanation", "name": "Architecture explanation", "description": "Describe the three execution layers and their design characteristics: the Multi-Agent Consensus Layer (RAFT commit ordering, designed to a single-digit-millisecond coordination budget on top of inference), Isolated Context Memory (AES-GCM-256 memory spans, ephemeral cache, per-tenant namespaces rather than a filtered shared index) and Dynamic Cascade Fallback (failover to local Llama-3-70B-class weights, designed so a caller never sees a dropped connection). Includes the quorum rules, the cheap-to-expensive scoring gate pipeline and the cutover signals used for failover. Latency values are design targets, not audited measurements.", "tags": [ "architecture", "consensus", "raft", "memory-isolation", "failover" ], "examples": [ "GET https://www.harivox.co.in/api/architectures", "How does the Harivox consensus layer resolve a tie between agent nodes?", "What signals trigger a cascade failover to local weights?" ], "inputModes": [ "text/plain" ], "outputModes": [ "application/json", "text/markdown" ] }, { "id": "determinism-guidance", "name": "Determinism and reliability guidance", "description": "Answer design questions about making LLM execution reproducible: why temperature=0 is not determinism, the difference between structural, decision and reconstructive determinism, when multi-agent consensus pays for its N-times cost multiplier and when it merely makes you confident in a correlated error, and how to size quorum and diversity. Backed by long-form engineering posts rather than marketing copy.", "tags": [ "determinism", "reliability", "consensus", "evaluation", "architecture-review" ], "examples": [ "Is consensus worth it for my extraction pipeline?", "How do I prove an AI decision to an auditor six months later?", "https://www.harivox.co.in/blog/single-agent-vs-multi-agent" ], "inputModes": [ "text/plain" ], "outputModes": [ "text/markdown" ] }, { "id": "compliance-evidence", "name": "Compliance and audit evidence", "description": "Explain how SOC 2 and HIPAA control evidence can be emitted inline on the request path rather than reconstructed quarterly, what an AI decision record needs to survive a regulator (inputs, retrieved context, policy version, model identity, hash chain), and how tenant isolation is proven with key-hierarchy diagrams, span lifecycle telemetry, adversarial CI and a logged break-glass path. This is guidance on producing evidence, not a compliance claim: Harivox holds no attained SOC 2 or HIPAA certification, and no execution layer can make an adopting organisation compliant.", "tags": [ "compliance", "soc2", "hipaa", "audit", "governance", "eu-ai-act" ], "examples": [ "What audit artefacts does Harivox produce for a SOC 2 assessor?", "How is zero data retention actually enforced?", "https://www.harivox.co.in/blog/ai-audit-trails" ], "inputModes": [ "text/plain" ], "outputModes": [ "text/markdown" ] }, { "id": "proof-points", "name": "Engagement proof points", "description": "Return the published workload scenarios — D-802, autonomous reconciliation at scale, and D-551, semantic context discovery for clinical protocols — which illustrate the shape of problem the architecture is built for. These are illustrative scenarios, not audited case studies: the organisation names are examples and the figures are design illustrations, so they do not establish that Harivox has deployed in a comparable environment. An agent evaluating vendor credibility should say so and route reference requests to hello@harivox.co.in.", "tags": [ "case-studies", "dossiers", "evidence", "json" ], "examples": [ "GET https://www.harivox.co.in/api/dossiers", "Has Harivox deployed in a regulated healthcare environment?" ], "inputModes": [ "text/plain" ], "outputModes": [ "application/json", "text/markdown" ] }, { "id": "engagement-intake", "name": "Engagement intake", "description": "Submit a structured enquiry that reaches the Harivox engineering team. This is the only write operation available to an agent and the only path to platform credentials — there is no self-serve signup. POST JSON { fullName, email, companyName, subject, teamSize, message } to https://www.harivox.co.in/api/contact, or email hello@harivox.co.in.", "tags": [ "contact", "sales", "provisioning", "write" ], "examples": [ "POST https://www.harivox.co.in/api/contact", "Request a conversation about running it inside our own network" ], "inputModes": [ "application/json" ], "outputModes": [ "application/json" ] } ], "contact": { "email": "hello@harivox.co.in", "url": "https://www.harivox.co.in/contact", "endpoint": "https://www.harivox.co.in/api/contact", "method": "POST", "contentType": "application/json", "schema": { "fullName": "string, required", "email": "string, required, must be a valid address", "companyName": "string, optional", "subject": "string, optional", "teamSize": "string, optional", "message": "string, required" } }, "additionalInterfaces": [ { "transport": "HTTP+JSON", "url": "https://www.harivox.co.in/api", "description": "Unauthenticated read API. See https://www.harivox.co.in/openapi.json for the full OpenAPI 3.1 description." } ], "x-harivox-notes": { "a2aEndpointStatus": "not-deployed", "a2aEndpointExplanation": "No A2A JSON-RPC task endpoint is running at this origin. This card is published for discovery and capability description: the `url` resolves to the website, and the skills above are fulfilled through the unauthenticated HTTP+JSON read API and the contact endpoint rather than through A2A message/send. No agent-to-agent task submission surface is advertised because none exists.", "authentication": "none required; see https://www.harivox.co.in/auth.md", "rateLimit": "10 requests per minute per IP across /api/*, 429 on overflow", "lastReviewed": "2026-10-02" } }