Accredible

Enable the Accredible connector in your fastn dashboard, then let each customer authenticate their own Accredible account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Accredible client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Accredible account and only ever sees their own learners, training records and credentials. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent verifies which credentials a recipient holds before answering.

fastn does. When Accredible changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Yes. An event in your product can enrol someone, assign a course, add them to a training path, or issue a credential in the customer's own Accredible account, so training and recognition follow what actually happened rather than a manual upload.

Yes, scoped per tenant and audited. Completions and issued credentials are frequently used as compliance evidence, so the read is logged and attributable rather than a bulk export nobody can trace.

A common starting point: issue certificates or badges from your product when a learner completes something. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Accredible does not change your per-connector cost. You can start free with 3 connected accounts.