AlphaBitCore

Agents take authenticated action in outside systems through a governed tool layer. Every model, agent, tool and workflow is invoked through one SDK and HTTP contract. The tool registry scopes every MCP server by authority, and the Workbench ships 10+ MCP connectors including primary financial data integrations. The Effector is the sole component holding durable mutation credentials and commits an external effect only within the scope the Gateway authorized. Beyond the connector catalog, customers can register their own MCP servers, internal APIs and data systems as tools.

SourceAlphaBitCore, alphabitcore.com (platform/unify, developers, home)read 2026-09-25

AlphaBitCore ships a multi step, multi agent runtime with a Planner (task decomposition and candidate actions), an Orchestrator, an Agent Runtime and a Skills and Tool Registry, and customers can bring LangGraph, Bedrock or Temporal instead. Workflows compose skills, tools and models into governed pipelines (95 in the Workbench), and Agent Teams run a Team Room that calls member agents and returns one synthesized answer.

SourceAlphaBitCore, alphabitcore.com (developers, home, developers/mcp)read 2026-09-25

Context is assembled per run from connected sources, not held in a maintained retrieval structure over the customer's corpus. Workbench agents pull entity, financials, holdings and news through workflows and MCP connectors, and the invocation contract can call a retrieval service the customer already runs. There is no index, graph or embeddings layer that AlphaBitCore maintains over the customer's documents, and the Nexus gateway's semantic cache stores responses, not knowledge.

SourceAlphaBitCore, alphabitcore.com (Workbench agents, platform/unify, nexus)read 2026-09-25

A person approves before the action commits, and the customer sets what needs sign off. A Prime execution suspends with status HITL_REQUIRED, and the owner approves, rejects or cancels it (from an MCP client or the Prime Console) before it continues. Policy as code at the Gateway evaluates scope, authority and guardrail rules on every call, and a denied execution produces zero state change and a sealed denial. The Workbench adds a tiered supervisory approval queue with role aware routing.

SourceAlphaBitCore, alphabitcore.com (developers/mcp section 4, platform/govern, home)read 2026-09-25

Access controls are in place, and a compliance audit is still pending. Every call carries a verifiable caller identity through one identity plane, and the Gateway federates with the enterprise identity provider (OIDC, SPIFFE and workload identity, specified per deployment).

Prime MCP signs users in with OAuth 2.0 and PKCE and derives tenant, user and role from the token, scope and authority policies are bound to each agent, and the supported gateway tier offers enterprise SSO and SCIM. The SOC 2 program is in progress, with the audit roadmap and third party attestations shared only in private briefings. Framework mappings are published, but they describe posture, not a completed audit.

SourceAlphaBitCore, alphabitcore.com (trust, platform/unify, developers, developers/mcp, pricing)read 2026-09-25

Every governed execution writes a signed, append only, Merkle sealed event stream with each stage (authorized, planned, executed, sealed) and a capability result envelope naming what was invoked and its inputs, so a customer can inspect each run after the fact. Denials are recorded as sealed events too.

An Inspection, Replay and Monitoring plane reads from the stream for audit, anomaly detection and forensics, and any execution can be re-run from its sealed stream. Execution Attestation Certificates are issued under the customer's keys, and the stream exports to SIEM and observability tooling.

SourceAlphaBitCore, alphabitcore.com (platform/prove, developers, home)read 2026-09-25

Conversation state lasts within a session. A Prime conversation continues across messages through a conversation handle (handles expire after 15 minutes by default). There is no memory layer with a set scope and lifetime. The Context Store in the record plane captures replay inputs for audit, and the Nexus gateway's semantic cache stores responses. Neither is memory the agent reads to decide.

SourceAlphaBitCore, alphabitcore.com (developers/mcp sections 3 and 4, developers)read 2026-09-25

Three deployment shapes are offered, hosted (Prime only), customer VPC and on premises (all three tiers), with air gapped deployment named for sovereign data constraints. The open source Nexus gateway self hosts by default or deploys from AWS Marketplace. Residency and processing region are specified per deployment, and single tenant and multi tenant patterns are both supported.

SourceAlphaBitCore, alphabitcore.com (pricing, trust, nexus)read 2026-09-25

The Investment and Wealth Workbench ships 23 named prebuilt agents for a customer to adopt, each built for one job and usable as shipped (8 research, 7 portfolio, 4 client communications, 4 compliance operations), on 95 workflows and 78 skills. Each stands on its own, and the Equity Screener, the Performance Attributor and the Risk and Scenario Analyst each do their own work without the others. The Workbench is in active design partner deployments and is included in the Prime tier.

SourceAlphaBitCore, alphabitcore.com (Workbench agents, home, pricing)read 2026-09-25

Work reaches an agent when a caller sends it, either a user in the Prime app or an external assistant (ChatGPT, Claude, Copilot, Codex) delegating a task through Prime MCP. Those are ways to call an agent, not events that start one, and there is no schedule, webhook or event source. The Market and Earnings Briefer describes daily briefings, but AlphaBitCore does not say what runs them.

SourceAlphaBitCore, alphabitcore.com (developers/mcp, Workbench agents)read 2026-09-25

Model choice and routing sit with the customer. The Nexus AI Gateway, the model layer of the AlphaBitCore stack, carries 20 provider codecs (OpenAI, Anthropic, Gemini, Vertex, Azure, Bedrock, Cohere and others, plus OpenAI compatible passthrough for Mistral, Groq, DeepSeek and more), routes across hosted and self hosted models, and policy checks every provider selection. The unified invocation contract makes switching providers a routing decision, with hosted and local models on one contract.

SourceAlphaBitCore, alphabitcore.com (nexus, platform/unify)read 2026-09-25

Outside callers can drive the platform. Prime MCP is the product's interface, with a published endpoint (https://finance.alphabitcore.io/mcp, Streamable HTTP, tenant format documented), a published auth scheme (OAuth 2.0 authorization code with PKCE and a documented discovery chain) and six enumerated tools that start real Prime tasks and answer approvals. Every model, agent, tool and workflow is also invoked through one SDK and HTTP contract, though the API reference is gated behind an evaluation.

SourceAlphaBitCore, alphabitcore.com (developers/mcp, developers, platform/unify)read 2026-09-25

Nothing tests or scores what an agent produces. Deterministic replay and ValidatePoE verification prove that a recorded execution is complete and reruns to the same result, which is audit repeatability, not a test of output quality. Policies are code that can be diffed and tested, but there is no harness, scored test cases or quality gate for agent output, and the gateway benchmark is AlphaBitCore's own measurement of its product.

SourceAlphaBitCore, alphabitcore.com (platform/prove, platform/govern, nexus)read 2026-09-25

No agent operates a browser or desktop. The closest thing is the Nexus gateway's Desktop Agent, which intercepts AI traffic at the operating system network layer (pf, iptables, WinDivert) so it passes through the compliance engine, but it navigates nothing.

SourceAlphaBitCore, alphabitcore.com (nexus)read 2026-09-25