Trust for communities and networks

The problem

Invite-only communities scale badly: admission depends on somebody already knowing the applicant, which quietly reproduces whoever is already inside.

Open communities have the opposite failure: throwaway accounts, and no way to tell a new member from a bad-faith one until after the damage.

Reputation earned in one community is worth nothing in the next, so every member starts from zero forever.

The solution

• A prospective member presents a share token or an export bundle. You check it without an API key, and without them creating an account with you first.
• Gate on the band rather than the number when you only need a coarse answer: the member can share at band-only or minimal scope and keep the detail private.
• Batch-read scores for an existing roster in one call when you want to review or tier your membership.
• Show verified standing in-product with the embeddable badge, which stops resolving the moment the member revokes their token.

How it works

Because verification is public, this flow works for a community that has no backend of its own: the check can happen in the browser.

The API calls involved

• GET/api/v1/verify/{token}Resolve a member’s share token. Public, no key.
• GET/api/v1/verify/{token}/exportSelf-verifying bundle for offline admission checks.
• POST/api/v1/users/scoresReview an existing roster: up to 100 members per call.
• GET/api/v1/users/{id}/score/componentsComponent view when you tier members by strength.
• POST/api/v1/webhooksReact to score.band_changed to promote or review a member automatically.

<!-- Show verified standing on a member profile -->
<div data-credda-badge data-token="MEMBER_SHARE_TOKEN"></div>
<script src="https://api.credda.io/widget/credda-widget.js" async></script>

Full request and response shapes are in the API reference.

Start building