Vulcan Technologies
Vulcan Technologies builds frontier AI for law and government, headquartered in Austin, Texas and founded in 2025. Its flagship product, Justinian, is a legal AI agent that runs on roughly 157 billion records of American law and policy — including 13+ billion court records, every municipal code, and federal and state statutes, regulations, and active legislative sessions — planning research, drafting work product, and verifying and citing every claim against source. A second product, Trajan, is a government AI concierge for citizen services such as permits, registrations, and license renewals. Vulcan is FedRAMP Ready, runs in AWS GovCloud (US), and serves customers including the Virginia Office of Regulatory Management, the U.S. Department of Education, and South Carolina agencies. The company raised a $10.9M seed round (October 2025) co-led by General Catalyst and Cubit Capital, with participation from Y Combinator, SV Angel, and others. Vulcan is a product/agent company and does not currently publish a public developer API.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Vulcan Technologies the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
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. From those artifacts we compute the Kin Score — Vulcan Technologies scores 17.7/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Vulcan Technologies
Each block below is one kind of artifact we hold for Vulcan Technologies. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Vulcan Technologies — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/vulcan-technologies · machine-readable index on apis.io