Crypto APIs MCP integration for AI agents.
Connect AI agents to Crypto APIs through 5 structured actions, including get asset details by id, get asset details by symbol, and get exchange rate by asset…
- ACTION CONTRACTS
- 5
- 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 Crypto APIs integration exposes
The Crypto APIs Agent App exposes 5 provider-backed actions for finance, data, and developer tools work. Its current contract lets an authorized agent get detailed crypto apis market data for one asset by its crypto apis reference id, get detailed crypto apis market data for one asset by its asset symbol, and get the exchange rate for one crypto apis asset reference id versus another asset reference 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 Crypto APIs account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Crypto APIs capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_asset_details_by_idREADGet detailed Crypto APIs market data for one asset by its Crypto APIs reference ID.
INPUTS: assetId / context
get_asset_details_by_symbolREADGet detailed Crypto APIs market data for one asset by its asset symbol.
INPUTS: assetSymbol / context
get_exchange_rate_by_asset_idsREADGet the exchange rate for one Crypto APIs asset reference ID versus another asset reference ID.
INPUTS: fromAssetId / toAssetId / context / calculationTimestamp
get_exchange_rate_by_symbolsREADGet the exchange rate for one asset symbol versus another asset symbol from Crypto APIs.
INPUTS: fromAssetSymbol / toAssetSymbol / context / calculationTimestamp
list_supported_assetsREADList fiat and cryptocurrency assets supported by Crypto APIs market data endpoints.
INPUTS: context / limit / offset / type
INPUT CONTRACTS
Know what the action needs before it runs.
get_asset_details_by_id
assetIdREQUIRED- The unique Crypto APIs reference ID for the asset.
contextOPTIONAL- A client-provided context value returned by Crypto APIs to correlate responses with requests.
get_asset_details_by_symbol
assetSymbolREQUIRED- The asset symbol in Crypto APIs listings.
contextOPTIONAL- A client-provided context value returned by Crypto APIs to correlate responses with requests.
get_exchange_rate_by_asset_ids
fromAssetIdREQUIRED- The base asset reference ID to get a rate for.
toAssetIdREQUIRED- The relation asset reference ID in which the base asset rate is displayed.
contextOPTIONAL- A client-provided context value returned by Crypto APIs to correlate responses with requests.
calculationTimestampOPTIONAL- The optional UNIX timestamp for historical market data used to calculate the exchange rate. Crypto APIs supports up to 30 days back.
get_exchange_rate_by_symbols
fromAssetSymbolREQUIRED- The base asset symbol to get a rate for.
toAssetSymbolREQUIRED- The relation asset symbol in which the base asset rate is displayed.
contextOPTIONAL- A client-provided context value returned by Crypto APIs to correlate responses with requests.
calculationTimestampOPTIONAL- The optional UNIX timestamp for historical market data used to calculate the exchange rate. Crypto APIs supports up to 30 days back.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Asset Details By Id
Get detailed Crypto APIs market data for one asset by its Crypto APIs reference ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_asset_details_by_idVerify with Get Asset Details By Symbol
Get detailed Crypto APIs market data for one asset by its asset symbol. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_asset_details_by_symbolSAFETY BOUNDARY
Operate Crypto APIs with explicit limits
- Authorize Crypto APIs with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Crypto APIs data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Crypto APIs rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Crypto APIs task completed successfully.
CONNECTION MODEL
API key
Crypto APIs API key sent with the x-api-key header. Create and manage API keys in the Crypto APIs dashboard at https://app.cryptoapis.io/login.
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
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- 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 Crypto APIs.