For developers

API

A free, read-only, keyless JSON API over the same connected knowledge graph you can browse on the site — entity records, sourced relationships, and Chokepoint Scores, structured for other tools and AI engines to pull directly rather than scrape.

v1, early and free. No API key required yet, and nothing here exposes anything beyond what's already visible on the public entity pages — this is a structured way to reach the same data, not new data access. Rate limits are enforced only via response caching for now (see below); a documented, higher-volume/paid tier is on the roadmap as usage grows.

List entities

GET /api/public/v1/entities

Query params (all optional): limit (default 50, max 100), offset, type (e.g. company, technology, person), category (e.g. Networking), and q (matches display name or aliases).

curl "https://insightnodes.com/api/public/v1/entities?type=company&limit=5"
{
  "total": 214,
  "limit": 5,
  "offset": 0,
  "count": 5,
  "results": [
    {
      "id": "nvidia",
      "displayName": "NVIDIA",
      "type": "company",
      "category": "Semiconductors",
      "strategicImportance": "Critical",
      "confidence": 98,
      "chokepointScore": 91,
      "url": "https://insightnodes.com/technology/nvidia"
    }
  ]
}

Get a single entity

GET /api/public/v1/entities/{id}

Returns the full record: summary, corporate profile, relationships (with resolved target names), milestones, sourced evidence, market intelligence (clearly labeled unverified claims), strategic risks, future outlook, Chokepoint Score, and Relationship Velocity. The id is the same slug used in the entity's page URL, e.g. nvidia for insightnodes.com/technology/nvidia.

curl "https://insightnodes.com/api/public/v1/entities/nvidia"

Notes

  • Caching: responses are cached at the edge for 5 minutes (longer while stale-revalidating) — the underlying data changes on the order of hours/days, not seconds, so this is both a performance optimization and the main abuse safeguard until a proper rate limiter/API key exists.
  • Stability: this is a v1, early product. Field names are intended to stay stable, but the API itself may evolve before a formal v2/versioning policy is published.
  • Attribution: if you build something with this, a link back to the entity's InsightNodes page (the url field in every response) is appreciated but not required.
  • Questions or heavier use case? Email hello@insightnodes.com.