Locus
Consortium membership

A consortium you join.

OpenData.org is a consortium of institutions that sustain a shared, attributed reference fabric. Locus is the engine that serves it. Membership is an agreement and a seat at the table, with terms set in conversation with the consortium.

What members get

The benefits, stated plainly.

Layer access as released
Every reference layer the consortium onboards, the moment its release gate opens: one catalog, the same for every member.
The attributed-answer contract
Every figure carries its source, authority class, and vintage: full papers on every answer, guaranteed by contract.
Governance participation
Members sit in the layer-onboarding and vintage-promotion decisions: which sources join the fabric, and when a new vintage starts serving.
Vintage-change briefings
When a layer moves vintages, members receive the change briefing before the switch: what moved, what stayed, what to re-check.
Partner support
An engineering contact who answers with the same precision the API does, straight from the contract.
How membership works

Apply, agree, onboard.

  1. Apply

    Write to membership@opendata.org with who you are and what you need located. We respond within 5 business days.

  2. Agreement

    One membership agreement with the consortium. Licensed sources (postal validation, parcel cargo) add their own acknowledgement gates inside the console, versioned and audited.

  3. Onboarding

    Your organization is provisioned, your org-admin invites the team, keys mint in the console, and the first resolved address lands the same day.

Membership classes

Three classes, described by capability.

A class is a named capability set, enforced as entitlement flags in the console. Which class fits is settled in the membership conversation.

Sandbox

The evaluation class. Everything behaves exactly as production does, against the sample corpus, with test keys.

  • Resolve, folio, and detail lookups against the sample corpus
  • Test keys only; no billing instrument, ever
  • The complete response surface: every arm and attribution tag
Member

The working class of the consortium: the production surface, with layers arriving as the consortium releases them.

  • Production resolve, folio, and detail lookups
  • Reference and hazard layers as released
  • Licensed cargo (parcel record, postal validation) behind their acknowledgement gates
  • Synchronous bulk resolve and usage export
Enterprise

Member, plus the surfaces an institution needs around the engine.

  • Scheduled bulk with delivery to your own storage
  • Portfolio monitoring as second vintages arrive
  • Single sign-on for your organization
  • Bespoke agreement paper (DPA, SLA) and custom onboarding

Apply for membership

Applying starts a conversation with the consortium. Tell us who you are and what you need located; we respond within 5 business days.

Apply for membershipmembership@opendata.org