Authenticate using your Accredible API key as Authorization header value (format: Token token=YOUR_KEY) against base URL https://api.accredible.com/v1
Create or retrieve a credential group (analogous to a certificate template) via GET /v1/issuer/groups; note the group_id for your target credential design
POST to /v1/credentials with body: {"credential": {"group_id": 12345, "recipient": {"name": "Jane Doe", "email": "jane@example.com"}, "issued_on": "2025-01-15", "complete": true}}; the complete:true flag triggers immediate email delivery
On success the response returns an id (credential_id) and a url field pointing to the publicly accessible certificate page
Retrieve issued credentials for a group via GET /v1/credentials?group_id=12345&page=1&page_size=50 for paginated listing
Revoke a credential by calling DELETE /v1/credentials/{credential_id}; the public URL becomes inactive immediately
Known gotchas
Setting complete:false creates the credential without sending the delivery email; forgetting to later PUT complete:true means recipients never receive their certificate
The Accredible API rate limit is not publicly documented; batch creation of hundreds of credentials should use delays between requests to avoid 429 errors
Group IDs are not portable across Accredible accounts; hardcoding group_id from a sandbox account will cause 404 errors in production
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp