Accredible Certificates MCP integration for AI agents.
Connect AI agents to Accredible Certificates through 8 structured actions, including get credential, create credential, and delete credential. Review authent…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Accredible Certificates integration exposes
The Accredible Certificates Agent App exposes 8 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get one accredible credential by credential id, create one accredible credential using json recipient and group fields, and delete one accredible credential by credential id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Accredible Certificates account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Accredible Certificates capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_credentialREADGet one Accredible credential by credential ID.
INPUTS: id
create_credentialWRITECreate one Accredible credential using JSON recipient and group fields.
INPUTS: id / group_id / recipient.name / recipient.email / recipient.phone_number
delete_credentialHIGH IMPACTDelete one Accredible credential by credential ID.
INPUTS: id
get_groupREADGet one Accredible credential group by group ID.
INPUTS: group_id
list_credentialsREADList Accredible credentials with documented query filters.
INPUTS: group_id / email / recipient_id / license_id / start_date
list_groupsREADList Accredible credential groups available to the API key.
search_credentialsREADSearch Accredible credentials with documented filters.
INPUTS: group_id / recipient.name / recipient.email / recipient.id / recipient.meta_data
search_groupsREADSearch Accredible credential groups with documented filters.
INPUTS: ids / name / course_name / department_id / meta_data
INPUT CONTRACTS
Know what the action needs before it runs.
get_credential
idOPTIONAL- The Accredible credential identifier.
create_credential
idOPTIONAL- The issuer-defined credential ID.
group_idREQUIRED- The Accredible group ID.
recipient.nameREQUIRED- The recipient name.
recipient.emailREQUIRED- The recipient email address.
recipient.phone_numberOPTIONAL- The recipient phone number.
delete_credential
idOPTIONAL- The Accredible credential identifier.
get_group
group_idOPTIONAL- The Accredible group ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Credential
Get one Accredible credential by credential ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_credentialControl Create Credential
Create one Accredible credential using JSON recipient and group fields. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_credentialVerify with Get Group
Get one Accredible credential group by group ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_groupSAFETY BOUNDARY
Operate Accredible Certificates with explicit limits
- Authorize Accredible Certificates with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_credential` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Accredible Certificates rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Accredible Certificates task completed successfully.
CONNECTION MODEL
API key
Accredible API key sent in the Authorization header as Token token=<API key>. Create or view API keys from API Management in Accredible: https://help.accredible.com/s/article/how-do-i-find-my-integration-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Accredible Certificates.