AgentifAI
AgentifAI is a Portuguese enterprise conversational-AI company, headquartered in Braga, that builds AliceOS - a voice-first AI contact-center and autonomous agent platform purpose-built for the regulated banking and healthcare sectors. AliceOS is sold as a managed enterprise deployment rather than a self-serve developer product: it orchestrates multi-agent workflows across phone, WhatsApp, SMS, email and web, and integrates with core banking systems, CRMs, fraud engines, Hospital Information Systems and EMR/EHR platforms over REST, SOAP and OAuth, with SIP and CTI telephony adapters. Reference deployments include Santander, Banco BPI, Caixa Geral de Depositos, Vivalto Sante, Lusiadas Saude and Luz Saude. The company publishes a first-party llms.txt and a SafeBase trust center naming SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001:2023, PCI DSS v4.0.0 and HIPAA, but no public developer portal, API reference or machine-readable API contract.
AgentifAI is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
AgentifAI markets "Enterprise API Integration" and REST-based custom digital channels as AliceOS capabilities, but publishes no reference for them anywhere — no docs., api., developer. or app. subdomain resolves in DNS, /openapi.json and /api-docs return 404 on the only web host it runs, and the single published route to the platform is the "Talk to us" enterprise-demo form.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is AgentifAI's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://www.agentifai.com/talk-to-us→ HTTP 200https://www.agentifai.com/openapi.json→ HTTP 404https://www.agentifai.com/.well-known/api-catalog→ HTTP 404
AgentifAI is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/agentifai · machine-readable index on apis.io
This is an independent, third-party profile of AgentifAI, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.