Application programming interface (API) provisioning using decentralized identity

1 . A system, comprising:

a computing device comprising a processor and a memory; and

machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

identify a provider decentralized identifier (DID) associated with an application programming interface (API) provider; and

establish a communication session with a provider DID agent associated with the API provider;

send a request for API key for access to a resource provided by the API provider, the request for the API key being transmitted via the communication session;

obtain a verifiable credential (VC) in response to the request, the VC comprising the API key;

submit an API call to an API provider service associated with the API provider for the resource; and

receive the resource from the API provider service in response to the API call and proving ownership of the API key.

2 . The system of claim 1 , wherein the API call comprises the VC or a cryptographic proof of the API key.

3 . The system of claim 1 , wherein the machine-readable instructions further cause the computing device to at least query a trusted provider registry to identify the API provider.

4 . The system of claim 1 , wherein the request includes a DID associated with a user of the computing device, the VC with the API key being obtained in response to the user being verified based at least in part on the DID.

5 . The system of claim 1 , wherein the resource comprises a first resource, the API call comprises a first API call, and the machine-readable instructions further cause the computing device to at least:

submit a second API call to the API provider service, the second API call comprising the API key or a cryptographic proof of the API key; and

receive a second resource from the API provider service in response to the second API call.

6 . The system of claim 1 , wherein the VC is issued by the provider DID agent associated with the API provider service, and the VC being obtained via the communication session.

7 . A method, comprising:

identifying an application programming interface (API) provider for obtaining a resource based at least in part on one or more resource criteria;

obtaining a decentralized identifier (DID) associated with the API provider from a trusted provider repository;

initiating an API key request for an API key to a provider DID agent identified from a DID document associated with the DID

determining that the API key has been provided; and

sending an API resource request for the resource to an API service provider, the API resource request including the API key.

8 . The method of claim 7 , wherein the API provider is one of a plurality of API providers and the trusted provider repository comprises API data associated with a plurality of APIs provided by a plurality of API providers.

9 . The method of claim 8 , wherein the API provider is identified based at least in part on a comparison of the one or more resource criteria and the API data associated with the plurality of APIs provided by the plurality of API providers.

10 . The method of claim 7 , wherein initiating the API key request comprising establishing a communication with the provider DID agent via a uniform resource locator (URL) obtained from the DID document.

11 . The method of claim 7 , further comprising receiving a verifiable credential (VC) from the provider DID agent, the API key being included in the VC.

12 . The method of claim 11 , wherein the API resource request comprises an API call, and the API key being included in the API call as the VC or a cryptographic proof associated with the API key.

13 . The method of claim 7 , wherein the DID comprises a provider DID and the API key request including a consumer DID associated with a user, the API key being provided in response to the user being verified by the provider DID agent based at least in response to the DID.

14 . A system, comprising:

a computing device comprising a processor and a memory; and

machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

receive a request for an application programming interface (API) key from a decentralized identifier (DID) agent associated with a user;

verify the user based at least in part on a verification of a credential document associated with the user;

generate a verifiable credential (VC) including the API key; and

transmit the VC to the DID agent.

15 . The system of claim 14 , wherein the request comprises a DID associated with the user.

16 . The system of claim 15 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

fetch a DID document associated with the user from a distributed identity ledger, the DID document being fetched based at least in part on the DID associated with the user.

17 . The system of claim 16 , wherein the credential document is obtained via the DID document.

18 . The system of claim 14 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

generate a mapping associating the API key with the DID of the user; and

provide the mapping to an API provider service.

19 . The system of claim 14 , wherein the VC further defines at least one of an expiration date for the VC or one or more limitations for using the API key.

20 . The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least obtain the DID associated with the API provider from a trusted provider repository.