Developers
Build on the same evidence model.
One OpenAPI 3.1 contract, scoped workspace tokens, structured errors and rate-limit signals, for typed clients, pipelines and agents.
curl "https://api.veriom.ai/v1/workspaces/$WORKSPACE_ID/findings?severity=high&limit=1" \
-H "Authorization: Bearer $VERIOM_API_TOKEN"
{
"items": [{
"id": "8c1e5f2a-…",
"title": "payments-api reaches card-vault outside the egress policy",
"risk_severity": "high",
"architecture_confidence": "0.91",
"lifecycle_state": "persistent",
"source_label": "IaC misconfiguration check",
"source_tools": [{ "tool": "iac_misconfiguration_check", "version": "3.2", "rule_id": "CKV_AWS_382" }]
}],
"has_more": true,
"next_cursor": "eyJvZmZzZXQiOjF9"
}Start from a contract
Give tools a precise surface, not a guessed one.
The contract names each operation, input, response, scope, failure and throttle signal, so generated clients and function tools behave predictably.
API reference
Every endpoint with its parameters, responses and code samples, and a playground that sends real requests with your API token. Typed clients come from the OpenAPI 3.1 contract behind it.
Authentication and scopes
Use customer sessions for the application, or expiring workspace tokens with one of 25 least-privilege scopes.
Typed failures
Every API error is application/problem+json with a stable code, a recovery hint and a request ID.
Self-throttling
RateLimit-Policy and RateLimit describe live quota state; HTTP 429 also includes Retry-After.
Pipelines and clouds
Put the same evidence model in your pipeline.
Three CI actions for GitHub, GitLab and Bitbucket, each with one workspace token and only the scopes listed. The workspace, repository, commit and run are detected for you.
name: Veriom architecture gate
on:
pull_request:
permissions:
contents: read
jobs:
architecture:
runs-on: ubuntu-latest
steps:
- uses: Veriom/actions/architecture-check@v2
with:
api-token: ${{ secrets.VERIOM_API_TOKEN }}Architecture gate
Audits the exact pull-request commit and fails the check from your workspace policy’s gate outcome. Mark it as required to make it a merge gate.
- audits:read
- audits:write
- repositories:read
Cloud inventory
Runs the read-only collector against your authenticated AWS, Azure or Google Cloud CLI and submits the inventory. Cloud credentials stay in your environment.
- evidence:write
Deployment records
Records a CI-attested deployment for the exact commit and run, so architecture changes line up with what shipped.
- evidence:write
No checkout is needed: Veriom audits the commit through its repository connection. GitLab CI and Bitbucket Pipelines use the same check through a generated template.
Context and tools
Give assistants the same model, inside the same boundary.
The MCP gateway and the documentation cover everything an agent or an integration needs.
- Veriom MCPConnect Claude, Cursor, VS Code, ChatGPT and other MCP clients over Streamable HTTP. They work as you, within your role and the scopes you allow.
- MCP tool manifestEvery veriom_ tool with its inputs, scope and read-only or destructive hints.
- DocumentationGuides for the API, the CI actions, cloud collectors and the CLI.
- llms.txtA plain-text map of the site and the docs for assistants.
Bring one bounded integration question.
Start with the public contract and the docs. Connect a production workspace once the scope and the review path are clear.