AI orchestration

OpenCentric Mesh: the AI router that eliminates B2B acquisition cost.

OpenCentric's AI scans businesses across the Catalog, detects capability gaps, and surfaces ranked solutions scored by SLA, SOW terms, trust signals, and business fit. The match comes to you, ranked by merit, not by who spent more on ads.

Supplier · venture profile

VLT

Veltro

SOC2 DevSecOps

Profile completeness94%

Tier 1 · Identity+20

Tier 2 · Capability+25

Tier 3 · Operational+27

Tier 4 · Trust signals+18

Tier 5 · Verified+10

$1.5K - $3.5K / moSOC2HIPAA-ready6-mo min

247views this week

5matches received

top 18%by completeness

North Health · match results

SOC2 DevSecOps under $3k/mo3 results

VLT

BESTVeltro

$2,500/mo · SOC2 · 99.95% · 94% complete

fit score

Sentinel Cloud

$2,800/mo · SOC2 · 99.9% · 84% complete

fit score

Bedrock Security

$1,900/mo · SOC2 · 99.5% · 61% complete

fit score

Source-blind ranking · mesh only

Capability Card Spec

The operating record behind every AI-routed resource.

Capability Cards replace vague listings with structured, verifiable resource data. Mesh can only route demand responsibly when suppliers expose what they do, who they serve, how they price, how they deliver, and what proof supports the claim.

Declare

Supplier or internal team publishes a structured capability with scope, terms, constraints, and proof.

Score

The card is scored for completeness, trust, commercial clarity, operational readiness, and verification.

Route

Mesh compares customer needs against card signals and ranks resources by fit, not ad spend.

Govern

Contracts, SOW terms, evidence, milestones, and customer outcomes remain attached to the card record.

Completeness model

Five tiers that make a card routeable.

Cards can appear in Catalog before they are fully verified, but Mesh ranking favors completeness, terms, evidence, and operational clarity.

Tier 1+20

Identity

Legal entity, category, owner, contact path, profile slug, and basic operating geography.

Tier 2+25

Capability

Structured service scope, pricing model, delivery capacity, exclusions, intake requirements, and proof points.

Tier 3+27

Operational

SLA posture, delivery model, support window, security baseline, minimum commitment, and acceptance criteria.

Tier 4+18

Trust signals

Certifications, customer outcomes, compliance posture, evidence links, team verification, and public references.

Tier 5+10

Verified

OpenCentric-reviewed completeness, source validation, business fit, and routing eligibility.

Schema fields

Field reference

Field	Type	Required	Description
id	string	Yes	Unique Capability Card identifier. Generated by OpenCentric.
displayName	string	Yes	Supplier, product, service, or resource name shown in Catalog and match results.
entityType	enum	Yes	One of: company, service, product, expert, studio, factory, apollo_campaign, internal_resource.
summary	string	Yes	One-sentence description used by Mesh for initial routing and human review.
capability	object	Yes	Structured category, services, outcomes, exclusions, requirements, and delivery model.
commercial	object	Yes	Pricing range, billing model, minimum term, SOW requirements, payment terms, and currency.
availability	object	Yes	Capacity, regions, response time, start window, support hours, and current status.
sla	object	No	Service level targets, response commitments, uptime, escalation path, and remediation terms.
compliance	object	No	Frameworks, evidence, certifications, control mappings, expiration dates, and readiness posture.
trustSignals	object[]	No	Case studies, testimonials, verified customers, references, security reviews, and audit artifacts.
routingSignals	object	Yes	Mesh scoring inputs: fit tags, industries, buyer stages, constraints, risk flags, and match rules.
verification	object	No	Completeness tier, reviewer, timestamps, evidence state, and OpenCentric verification status.
embed	object	No	Controls for external embeds, public visibility, approved domains, and analytics.
createdAt	ISO 8601	Yes	Timestamp for initial card creation.
updatedAt	ISO 8601	Yes	Timestamp for the latest supplier, system, or verification update.

Example payload

Structured for routing and governance

{
  "displayName": "Veltro",
  "entityType": "service",
  "summary": "SOC 2 DevSecOps support for healthcare SaaS teams.",
  "capability": {
    "category": "devsecops",
    "services": ["SOC 2 readiness", "secure CI/CD", "cloud controls"],
    "industries": ["healthcare", "B2B SaaS"],
    "deliveryModel": "managed_service"
  },
  "commercial": {
    "pricingModel": "retainer",
    "range": { "min": 1500, "max": 3500, "currency": "USD", "unit": "month" },
    "minimumCommitment": "6 months",
    "sowRequired": true
  },
  "compliance": {
    "frameworks": ["SOC 2", "HIPAA-ready"],
    "evidenceStatus": "available_under_nda"
  },
  "routingSignals": {
    "fitTags": ["under-3k", "soc2", "healthcare", "devsecops"],
    "responseWindow": "1 business day",
    "completenessScore": 94
  }
}

Verification note

Public cards can be self-declared. Verified cards require evidence review, current commercial terms, and enough operating data for Mesh to compare them against customer constraints.