Exporting entity data (JSON-LD)

Enterprise+ workspaces can export entity data from the Forum Network as JSON-LD — Linked Data in JSON form, with Schema.org and custom FedGrade vocabularies layered on top. JSON-LD makes the export consumable by graph databases, knowledge-graph pipelines, and downstream RDF tooling.

Tier requirement

Enterprise or Government tier. Lower tiers can browse the Network graph but cannot export structured payloads.

How to export

Three surfaces:

1. From the entity detail panel. Hit "Export entity" on any node's detail card. Returns the entity, its first-hop neighbors, and the citation provenance for each edge.
2. Bulk via the API. GET /api/network/graph?entityId=...&depth=2&format=jsonld returns the BFS expansion in JSON-LD shape. See the API docs.
3. Workspace archive. The workspace archive (see Data export) includes a network/ subdirectory of one JSON-LD file per known entity at export time.

Shape

The JSON-LD payload uses:

• @context — Schema.org for Organization, Person, GovernmentOrganization; custom FedGrade vocabulary at https://fedgrade.com/vocab/v1 for Contract, Program, Regulation, OMBMemo, ForecastPrediction, CitationProvenance.
• @id — the canonical entity URI, e.g., https://app.fedgrade.com/network/entity/agency:hhs.
• @type — the entity class.
• Domain properties — name, description, naicsCode, dunsNumber, cageCode, awardsTo, subcontractsTo, mentionedIn.

Each edge is reified as a node so the citation provenance is attachable — every relationship can be traced to the source document that established it.

Example

{
  "@context": {
    "@vocab": "https://schema.org/",
    "fg": "https://fedgrade.com/vocab/v1#"
  },
  "@id": "https://app.fedgrade.com/network/entity/agency:hhs",
  "@type": "GovernmentOrganization",
  "name": "Department of Health and Human Services",
  "fg:awardsTo": [
    {
      "@id": "https://app.fedgrade.com/network/edge/abc123",
      "@type": "fg:AwardRelationship",
      "fg:vendor": { "@id": "https://app.fedgrade.com/network/entity/vendor:bah" },
      "fg:contractValue": 145000000,
      "fg:citation": {
        "@id": "https://app.fedgrade.com/sources/notice/xyz",
        "fg:sourceTable": "notices"
      }
    }
  ]
}

Use cases

• Loading into Neo4j or Neptune for advanced graph queries
• Cross-referencing with internal CRM entities (vendor matching by DUNS / UEI)
• Feeding into RAG pipelines as structured entity context
• Compliance and audit — every edge carries a source pointer for reproducibility

Limits

• Per-query node cap: 500 (use pagination via cursor for larger expansions)
• Rate limit: 20 requests per minute per API key
• Person nodes are export-restricted to those with public-record affiliations only; private people in the people connector are not exported