Platform · Integration

One API core, every channel.

Identical calls produce identical results. The channel never changes the compliance outcome.

API core
RESTMCPiFrameUI
  • Live
  • Tested
  • Planned
OFAC SDNSanctionsOpenSanctionsSanctions & PEPRefinitiv World-CheckScreeningDow Jones Risk & ComplianceScreeningLexisNexisScreeningNewsAPI / EventRegistryAdverse mediaComplyAdvantageAdverse mediaOpenCorporatesUBOGLEIF / LEIUBOCompanies HouseUBOSEC EDGARFilingsOpenOwnership RegisterUBOOktaIdentity & SSO
Anthropic ClaudeLLMOpenAI GPTLLMGoogle GeminiLLMAWS BedrockLLMAzure OpenAILLMMeta LlamaOpen-weight LLMMistralOpen-weight LLMLoan origination systemsYour systemsCore bankingYour systemsCRMYour systemsOnboarding portalsYour systemsIDV / CIP providersYour systemsCase management & ESBYour systems
  • OFAC SDNSanctions
  • OpenSanctionsSanctions & PEP
  • Refinitiv World-CheckScreening
  • Dow Jones Risk & ComplianceScreening
  • LexisNexisScreening
  • NewsAPI / EventRegistryAdverse media
  • ComplyAdvantageAdverse media
  • OpenCorporatesUBO
  • GLEIF / LEIUBO
  • Companies HouseUBO
  • SEC EDGARFilings
  • OpenOwnership RegisterUBO
  • OktaIdentity & SSO
  • Anthropic ClaudeLLM
  • OpenAI GPTLLM
  • Google GeminiLLM
  • AWS BedrockLLM
  • Azure OpenAILLM
  • Meta LlamaOpen-weight LLM
  • MistralOpen-weight LLM
  • Loan origination systemsYour systems
  • Core bankingYour systems
  • CRMYour systems
  • Onboarding portalsYour systems
  • IDV / CIP providersYour systems
  • Case management & ESBYour systems
How you connect

Four doors, one core.

Every channel calls the same versioned API, so outcomes never depend on the channel.

HTTP
POST /v1/cases
Authorization: Bearer ••••
Content-Type: application/json

{ "subject": "SUB-88231", "type": "onboarding" }
ResponseSame result
{
  "case_id": "KYC-2026-0412",
  "decision": "PASS",
  "risk": "low",
  "elapsed_ms": 1400,
  "audit_hash": "sha256:9f2c…e41a"
}
Which channel fits

Pick the right door for each team.

Answer three questions. Most clients use more than one.

Who consumes it?
How fast must it respond?
Who owns the UX?

Answer all three questions to see a recommendation.

ChannelPrimary consumerLatencyEffortSecurityBest for
RESTsystems & middlewarelowest, direct callsmost control, most buildOAuth 2.0 / OIDC, mTLSSTP, deep embedding, volume
MCPAI agents & copilotsadds protocol overheadlow, tools self-describeinherits API entitlementsagentic workflows
iFrameend users in client portalsinteractive, UI-boundfront-end build onlytoken handoff, CSPembedded UX, white-label
What it plugs into

Your systems, connected.

Decisions and evidence flow back into the systems your bankers already use.

  • Loan origination systems

    A new application triggers KYC by webhook; Athena's decision and evidence are written back to the loan file.

    Connects via
    WebhookRESTBatch
  • Core banking

    Customer and account events start periodic and event-driven reviews; status syncs back automatically.

    Connects via
    EventsRESTBatch
  • CRM

    Prefills onboarding data and keeps the customer record current with every review.

    Connects via
    WebhookREST
  • Onboarding portals

    Embed Athena's checks with the iFrame or call the APIs from your own flow.

    Connects via
    iFrameREST
  • IDV / CIP providers

    Keep your preferred provider. PerceptaCore orchestrates its output and adds the investigation.

    Connects via
    RESTSDK
  • Case management & ESB

    Events flow through webhooks, batch and streaming; every action stays in one audit trail.

    Connects via
    WebhookBatchStreaming
Provider choice

Vendor-agnostic by design.

Swap data providers per category without touching client code.

Model choice

Bring your own LLM.

Route each task to the model your policy and residency rules allow.

Time to first call

Built for developers.

OpenAPI contracts and a sandbox in 24 hours shorten integration.

Where it runs

Deploy your way.

Move from SaaS to your own perimeter without re-integration.

How data is protected

Enterprise security, isolation and audit.

Tenant isolation and a full audit trail answer your security review up front.

IdentitySSO + scoped keys per tenant
IsolationEach client's data in its own space
AuditEvery action time-stamped and hashed

Identity & access

  • Okta OAuth 2.0 / OIDC
  • Mutual TLS
  • Per-function entitlements
  • Segregation of duties
  • MCP tools inherit API permissions

Data isolation

  • Postgres schema per tenant
  • Row-level security
  • Per-tenant KMS keys
  • Isolated audit trail
  • Local store option

Audit & reporting

  • Every Athena action time-stamped
  • Immutable versioned rule history
  • Full trail by subject and case
  • Scheduled and ad-hoc reports

Zero PII on-chain: only SHA-256 hashes reach the ledger.

Read our security overview →
~80% straight-through<2s decisions100% logged

Map your use cases to a channel and a deployment model.

Exam-ready audit trail · Zero PII on-chain · Your LLM, your cloud