Obtain your ECS Organization or Persona credential
The credential that says who operates your services. In standalone mode your agent holds it directly; it is issued by an organisation the ECS ecosystem accredited to verify legal entities (or personas), after an onboarding process your corporation starts and your agent runs.
Goal
An active Holder accreditation on the ECS Organization (or Persona) schema for your agent's DID, and the credential published in its DID Document.
Prerequisites
- A running agent in standalone mode with the organisation claims set (Configuration), and its DID.
- A corporation your account acts for, with a little balance on the agent's account (or a fee grant).
Steps
1. Choose a validator
In the frontend, Discover & Join, open the ECS ecosystem, select the Organization schema (or Persona if a person operates the service) and the role Holder. The wizard shows the accredited issuers as trust cards with their validation fee and the evidence they ask for. On testnet one or more demo issuers validate with light checks; on mainnet an accredited issuer will verify your legal entity against a registry.
2. Start the onboarding process
Enter your agent's DID. In the advanced section set your agent's account as VS operator and keep the proposed message types: they let the agent record sessions and trigger re-resolution for this accreditation. Review the cost: the validator's fee goes to escrow, a share goes to your corporation's trust deposit, plus network fees. Sign.
3. Let the agent run the flow
The agent sees the new pending accreditation through the indexer, connects to the validator's agent over DIDComm, and sends the onboarding request with the claims from your configuration. Watch the flow:
curl -s http://127.0.0.1:3000/v2/vt/flows | jq '.items[] | select(.variant=="onboarding-process") | {participantSessionId, flowState, connectionState}'
| Flow state | What is happening |
|---|---|
OR_SENT | Request sent; the validator reviews |
OOB_PENDING | The validator sent a link you must complete outside the agents (a form, a document upload). Read it from the flow record and complete it. |
VALIDATING | The validator is working |
VALIDATED then CRED_OFFERED | The validator set your accreditation active and is issuing |
COMPLETED | The credential is in your agent's store and published |
4. Nothing else
The agent publishes the credential as a linked presentation, triggers re-resolution, and keeps the connection to the validator open for later updates (renewal, revocation).
Verify
curl -s https://agent.example.com/.well-known/did.json | jq '.service[] | select(.type=="LinkedVerifiablePresentation") | .id'
shows an entry ending in org-vtc-vp (or persona-vtc-vp). The frontend's Agents page shows the accreditation as active.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The agent logs that the ecosystem is not trusted | The ECS ecosystem DID is missing from TRUSTED_ECS_ECOSYSTEM_DIDS | Add it and restart |
| The agent logs a claim error naming a URI | A *_URI resource could not be fetched | Serve it, or point at the placeholders |
Flow in OR_SENT for hours | The validator is offline or has not reviewed | Contact the validator through the channel its governance framework names; on testnet, pick another |
| Validator rejected | Evidence refused; the reason is in the flow record | Fix and re-apply; the escrowed fee is refunded on cancellation |
Next
- Issue your ECS Service credential.
- Specification: VS Agent v4,
VSA-VTI-ECS-STANDALONE; vt-flow protocol.