Integration
Connect CryptAPI to openSenseMap
When something happens in CryptAPI, your agent does the next thing in openSenseMap. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CryptAPI and openSenseMap to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CryptAPI and openSenseMap
Triggers and actions 1 trigger ยท 15 actions
Trigger
Payment received (instant)Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.
- Convert price
Convert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.
- Create payment address
Generate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.
- Estimate blockchain fees
Estimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.
- Generate payment QR code
Generate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.
- Get payment address logs
Get the callback/payment activity log for a previously created payment address, for a given ticker.
- Get ticker info
Get details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.
- List supported cryptocurrencies
List all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.
Action
Find measurements by phenomenonFetch the latest measurements for all sensors measuring a given phenomenon/grouptag, as JSON or CSV. GET /statistics/idw or /boxes/data (phenomenon-scoped query)
- Find senseBoxes near location
Search senseBoxes near a given coordinate/bounding box and phenomenon. GET /boxes with near/bbox query params
- Get 10000 latest measurements for sensor
Fetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters. GET /boxes/:senseBoxId/data/:sensorId
- Get database statistics
Fetch overview statistics about the openSenseMap database (box count, sensor count, measurement count). GET /stats
- Get latest measurements of senseBox
Fetch the latest measurements of all sensors for a given senseBox. GET /boxes/:senseBoxId/sensors
- Get latest measurements of sensor
Fetch the latest measurement value for one specific sensor of a senseBox. GET /boxes/:senseBoxId/sensors/:sensorId
- Get senseBox
Fetch details for one senseBox station by its ID. GET /boxes/:senseBoxId
- List senseBoxes
List all senseBox stations, optionally filtered by bounding box/phenomenon/exposure. GET /boxes
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews