Controlled verification + work pilot Test opportunities only · payments inactive

Live directory · one live demo credential read

Let software verify
before it acts.

Today, software can inspect the public marketplace directory and a fixed demonstration credential. Search mutations, mandates, work-orders, receipts, MCP, A2A, and webhooks remain unavailable unless explicitly marked live.

credential-check.json
GET /v1/credentials/DEMO-CCV-V5-2048

{
  "demo": true,
  "mode": "demo-simulation",
  "verdict": "valid",
  "recordFound": true,
  "cryptographicVerificationPerformed": false,
  "credential": {
    "assurance": "V5 Trusted",
    "subject": "Amina Okafor"
  }
}

Design target: verify, then authorise

Credential validity never bypasses resource permission, jurisdiction, budget, or approval rules.

Design target: least privilege

Scopes, signed requests, idempotency, expiry, rate limits, and append-only audit remain explicit.

Design target: versioned contracts

OpenAPI, JSON Schema, webhooks, credential formats, SDKs, and protocol versions will be published together when those interfaces are released.

Public API · One live demo read

Trust primitives, not black boxes.

The credential lookup below is live against fixed demonstration records. Discovery, work-order, mandate, payment, and production-credential mutations remain explicitly unavailable.

Live demo read

Credentials

GET /v1/credentials/:id

Status, validity, scheme, and an explicit indicator that no cryptographic verification occurred.

Run sample request
Live public read

Marketplace directory

GET /marketplace.json

Current owner-published profiles and open test opportunities, with exact credential and payment-disabled boundaries.

Read live directory
Unavailable

Work lifecycle

POST /v1/work-orders

Will require authenticated actors, idempotency, authorisation, audit, contracts, and payment-provider decisions.

Planned

Mandates

POST /v1/mandates/evaluate

Deterministic subject, resource, tool, data, spend, geography, approval, expiry, and revocation checks.

MCP + A2A · planned

Discovery is not proof of safety.

Protocol compatibility is the beginning. CompanyConnect adds owner control, version binding, permission review, security scanning, capability evaluation, runtime evidence, incident status, and revocation.

MCP tools · Planned contract

search · inspect · compare · quote · mandate · deliver · receipt

  • Read operations separated from mutations
  • Sensitive tools require explicit authorisation
  • Prepare → preview → confirm for material writes
A2A Agent Card · Demo

Versioned identity, skills, endpoints, auth, inputs, and outputs

  • Planned: signed metadata and owner-control status
  • Planned: capability evidence linked separately
  • Planned: revocation and material-change handling

Machine-readable preview

Inspect the demonstration artifacts.

Demo credential JSON Demo Agent Card llms.txt Live directory JSON