> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solo.one/llms.txt
> Use this file to discover all available pages before exploring further.

# Business graph

> What can actually be verified about a business in the network, and how each branch becomes a reusable trust asset

The **business graph** is everything a SOLO network can hold about a legal
entity: a core identity, plus the verification events participants have furnished
about it. Each branch is a candidate [trust asset](/concepts/trust/trust-assets)
— an attested verification another institution can reuse instead of repeating
registry lookups, ownership tracing, and risk screening.

This page shows what lives in the graph **today**. Every node maps to a real
model; branches with no backing model in the current catalog (for example
business financials/revenue, banking relationships, or tax-return inventories)
are deliberately absent rather than implied.

## The graph

```text theme={null}
Business
├── Identity                            (business)
│   ├── business_legal_name, business_dba_name
│   ├── business_jurisdiction_of_formation
│   ├── business_entity_type
│   ├── business_date_of_incorporation
│   ├── federal_ein / tax identifier
│   ├── business_website_url, business_email, business_phone
│   └── employee_count
│
├── Business identity verification      (business_identity_verification_event)
│   ├── registration_status, registration_identifier
│   ├── jurisdiction_of_formation, entity_type
│   ├── operational_existence_status
│   ├── tax_id_validation_result, address_verification_result
│   ├── is_secretary_of_state_match
│   └── formation_document_artifact (evidence)
│
├── Ownership & control                 (business_ownership_control_verification_event)
│   ├── beneficial_owners_identified_count
│   ├── control_persons_identified_count
│   ├── authorized_representatives_identified_count
│   ├── beneficial_ownership_determination_method
│   ├── beneficial_ownership_threshold_applied
│   ├── control_determination_basis
│   └── ownership_evidence_artifact (evidence)
│
├── Risk & compliance                   (business_risk_compliance_event)
│   ├── sanctions_screening_result
│   ├── adverse_media_assessment_result
│   ├── is_on_aml_watchlist, is_on_ofac_watchlist
│   ├── activity_risk_level
│   ├── restricted_activity_assessment_result
│   └── primary_activity_classification_code / system
│
└── Consent                             (business consent)
    └── scope, expires_at, consented_fields
```

## How to read the graph

* **Identity** is the [entity](/concepts/identity/entities) itself — the legal
  name, jurisdiction, and tax identifier that let contributions from different
  participants accrue to one business.
* **Verification branches** are furnished events. A
  [KYB certificate](/api-overview/querying/kyb-certificate) query consolidates the
  three verification branches — identity, ownership & control, and
  risk & compliance — into one certificate.
* **Registration and addresses** are not separate branches; they are fields
  inside business identity verification (`registration_status`,
  `business_registered_address`, `business_operating_address`).
* **Consent** is the permission layer that governs reading any branch.

## Each branch carries provenance

Every populated KYB sub-product carries the `furnishing_entity_id` and
`attestation_id` of the participant whose data backed it, plus an `assertions`
block recording what was asserted and when. Ownership and identity branches
reference concrete evidence artifacts (a cap table, articles of organization).
See [Provenance](/concepts/trust/provenance) for the full lineage model.

<Note>
  What you can actually read back is the intersection of the network's
  [querying policy](/concepts/governance/querying-policies) and your
  [entitlement](/concepts/governance/entitlement). The graph describes what
  *can* exist; consent, policy, and entitlement decide what *you* see.
</Note>

## Reusable trust assets for a business

Consolidated through products, the business graph yields reusable assets such
as:

* **Verified business identity** — registration, jurisdiction, and tax-ID
  validation from a [KYB certificate](/api-overview/querying/kyb-certificate).
* **Verified ownership** — beneficial owners and control persons, evidenced.
* **Risk & compliance screening** — sanctions, adverse media, and watchlist
  outcomes.

## Related

<CardGroup cols={2}>
  <Card title="Consumer graph" icon="user" href="/concepts/trust/consumer-graph">
    The equivalent for consumers.
  </Card>

  <Card title="KYB Certificate" icon="building" href="/api-overview/querying/kyb-certificate">
    The consolidated business trust asset, field by field.
  </Card>

  <Card title="Trust assets" icon="award" href="/concepts/trust/trust-assets">
    What makes a verification reusable.
  </Card>

  <Card title="Provenance" icon="fingerprint" href="/concepts/trust/provenance">
    The lineage each branch carries.
  </Card>
</CardGroup>