Registered Service Providers
Repository platforms, integrators, and consultancies that build on Ekayana and serve institutions through software those institutions already run. The Registered Service Provider program reviews and certifies those integrations. Ekayana is pre-launch, so nothing has been certified yet and the directory is empty.
Institutions adopt through the platforms they already run
Most institutions never call an API directly. They deposit through a repository, manage projects in a CRIS, and rely on the vendors and consultants who run those systems. For did:bio registration to become routine, it has to happen inside that software, at the moment a dataset is deposited. Registered Service Providers are the organizations that put it there.
Repository platforms
Dataverse installations, Zenodo style archives, institutional repositories
Deposit workflows that register a did:bio as part of publishing a record. Datasets keep the DOIs and Handles they already have, and the identifier is added alongside them.
Integrators and platform vendors
CRIS systems, lab informatics, research data management platforms
Products institutions already license, wired to the Ekayana REST API, UCAN delegation, and IPFS pinning so a registration happens without anyone leaving the tool they work in.
Consultancies and implementation teams
Onboarding, migration, compliance
The work that sits around the software: GDPR and data sovereignty reviews, metadata migrations, and rolling out the Ekayana Console across departments or a consortium.
What the program provides
Certification checks the parts of an integration that members depend on: registration, resolution, delegated authorization, and metadata good enough to be found again through knowledge-graph discovery. None of it is a prerequisite for building. The documentation is public, and any platform can integrate today without joining the program. Certification exists so that members can tell which integrations have been reviewed and are supported.
Technical access
- Certification review
- A documented checklist covering did:bio registration through the Bio-DID-Sequencer, public resolution, metadata quality, and UCAN capability delegation.
- Sandbox and integration support
- Integration guides, a sandbox against the Solana registry devnet, and an engineering contact for the questions documentation does not answer.
- Advance notice of changes
- API and schema changes announced before they land, with preview endpoints where an integration needs time to adapt.
Visibility and community
- Directory listing
- A listing in the Registered Service Provider directory, which the community team refers to when an institution asks how to adopt Ekayana through software it already runs.
- Provider calls
- Regular calls with the engineering team and early sight of the roadmap. Provider feedback goes to the steering groups that review the metadata schema and resolver behavior.
What certification does not confer
A Registered Service Provider integrates with Ekayana using each member's own credentials. Certification is a statement about the software, and it carries no right to register did:bio identifiers on behalf of organizations that are not members. Registrations made through a provider's integration count against that member's own allowance: 100,000 registrations a year and 100 GB of pinned IPFS storage are included in the annual service fee.
See the fee scheduleBecoming a Registered Service Provider
The path follows the membership process: an inquiry, a technical review with the community team, certification, then a listing. Since the platform has not launched, the first providers will work through it alongside the first member institutions.
Inquiry
Tell us what you build and which institutions you serve. The community team replies with program details and a technical starting point.
Technical review
A consultation covers the architecture: how the platform registers did:bio identifiers, how it handles UCAN capabilities, and how pinned content on IPFS is managed over time.
Integration certification
You demonstrate the integration against the checklist below. Testing runs in the sandbox, and the community team goes through the results with you.
Listing
The integration is added to the provider directory, and members can adopt Ekayana through software they already run.
What the review covers
- did:bio registration and DID document updates through the REST API
- Public resolution, including honest error handling when a record is missing or withdrawn
- Metadata complete enough to be useful in the knowledge graph and in semantic search
- UCAN delegation that is time bound, revocable, and least privilege
- GDPR aligned handling of consent, portability, and erasure requests
Records registered through a provider are also what BioAgents read and what the knowledge graph indexes, which is why metadata quality is part of the review. Most providers start with the platform overview and the workflow integration guide, which describe the endpoints the checklist tests.
The technology the platform is built on
The directory is empty. Ekayana has not launched, no integration has been certified, and there is nothing yet to list. What does exist is the stack underneath: open protocols, repository software, and identifier standards that Ekayana builds on, anchors to, or bridges into. These are technologies, not organizations. None of them is a partner, a member, or a certified provider, and their presence here is not an endorsement by the projects behind them.
Storage, networking, authorization
- IPFSBuilt on
- Content addressed storage. Every file and metadata record is addressed by its hash.
- libp2pBuilt on
- The peer-to-peer networking layer underneath IPFS transport and node discovery.
- FilecoinBuilt on
- Long term storage with cryptographic proofs that a copy is still held.
- UCANBuilt on
- Capability tokens for delegated authorization, so an integration acts within limits the member sets.
Registry, repositories, identifiers
- SolanaAnchored on
- The network the registry program writes to, making did:bio resolution tamper evident.
- DataverseBridges to
- Open source repository software. Bridged datasets keep their DOIs and gain a did:bio.
- ZenodoBridges to
- General purpose open repository, bridged on the same DOI preserving terms.
- ORCID iDsReferences
- Researcher identifiers referenced from did:bio metadata so people stay linked to their outputs.
Certified providers will be listed here once the program opens, alongside the first member institutions. Progress is posted on the research blog.
Build did:bio registration into your platform
Tell us what you build and which institutions you serve. The community team will walk through the technical review, certification, and listing.