Developers

Developer access is planned.

We would rather say that plainly than link to documentation that does not exist yet. Here is how we are approaching it, and how to be first in line.

Available today / Planned

Available today

No developer tools are publicly available yet: no API keys, endpoints or SDK packages.

Planned

Planned
  • API accessProgrammatic access to conversations and the outputs they produce.
  • Structured outputsResponses that follow a schema you define, so they slot into your own systems.
  • Tool connectionsA permissioned way for Vibrant to read from and act in the services you choose.

The shape we are designing toward

An artifact response might look like this. Field names are illustrative and will change before release.

Design goals

  • Predictable formats over clever ones.
  • Sources referenced explicitly in every output.
  • Versioned changes with clear notice.
Illustrative schemaExample only. Not a live API response.
{
  "type": "artifact",
  "format": "document",
  "title": "Repair café — first look",
  "status": "draft",
  "sources": [
    {
      "id": "src_1",
      "name": "repair-cafe-notes.md"
    },
    {
      "id": "src_2",
      "name": "volunteer-survey.csv"
    }
  ],
  "sections": [
    {
      "heading": "What we already have",
      "source_ids": [
        "src_1",
        "src_2"
      ]
    },
    {
      "heading": "Open questions",
      "items": [
        "Insurance for the venue",
        "Tool storage"
      ]
    }
  ]
}

Building something with Vibrant in mind?

Join developer early access and tell us what you would build.

Join developer early access