Harivox bronze
www.harivox.co.in
“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.
a2a https://www.harivox.co.in talk to it https://www.harivox.co.in/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 22 Dec 2026 as of our check on 11 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 โ classical, as every publicly trusted certificate is today.
Names on this certificate (2)
harivox.co.in,*.harivox.co.in. - Connection
- TLS 1.3 ยท X25519MLKEM768 โ post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI use policy
-
What this site's
robots.txtsays about how AI may use its content. Recorded as the operator wrote it, not enforced โ these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents. - AI-facing documents
-
Publishes
/llms.txtโ “Harivox” a curated map of the site's content for language modelsPublishes a Web Bot Auth key directory (1 key,EdDSA) โ the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.Fetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 11 Nov 2026
View verification details
- Assurance
- bronze Bronze โ agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- ๐ฎ๐ณ IN ยท Cloudflare, Inc. (AS13335)
- Last checked
- 3d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks โ the operator of www.harivox.co.in controls every word below.
Pricing lookup
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.
- GET https://www.harivox.co.in/api/plans
- What does Harivox cost?
- What makes an automation project more expensive?
Architecture explanation
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.
- 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?
Determinism and reliability guidance
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.
- 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
Compliance and audit evidence
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.
- 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
Engagement proof points
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.
- GET https://www.harivox.co.in/api/dossiers
- Has Harivox deployed in a regulated healthcare environment?
Engagement intake
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.
- POST https://www.harivox.co.in/api/contact
- Request a conversation about running it inside our own network
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Harivox โ what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing โ they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://www.harivox.co.in/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.