Integration
Connect Open Government, Finland to Blockscout
When something happens in Open Government, Finland, your agent does the next thing in Blockscout. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Open Government, Finland and Blockscout 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 Open Government, Finland and Blockscout
Triggers and actions 1 trigger · 25 actions
Trigger
New datasetFires when a new dataset is published to the Finnish open-data catalog (polls CKAN package_search sorted by creation date).
- Find datasets
Search the Finnish open-data catalog for datasets matching a keyword, tag, organization, or other criteria (CKAN package_search).
- Get dataset
Retrieve the full metadata and resource list for one published dataset by its id or name (CKAN package_show).
- Get organization
Retrieve details and datasets for one publishing organization by id or name (CKAN organization_show).
- Get resource
Retrieve one data resource (file/link/format) belonging to a dataset by its resource id (CKAN resource_show).
- List datasets
List the names of all published datasets in the catalog (CKAN package_list).
- List groups
List the topical groups/categories used to organize datasets in the catalog (CKAN group_list).
- List organizations
List the government organizations and agencies that publish datasets in the catalog (CKAN organization_list).
- List tags
List the tags used across datasets in the catalog, optionally filtered by a query string (CKAN tag_list).
Action
Find items by searchSearch across addresses, blocks, transactions, and tokens by query string. GET /search?q={query}
- Get address
Get detailed info about an address or contract (balance, type, etc). GET /addresses/{address_hash}
- Get block
Get detailed information about a block by number or hash. GET /blocks/{block_number_or_hash}
- Get smart contract
Get verified smart contract source, ABI, and metadata by address. GET /smart-contracts/{address_hash}
- Get stats counters
Get network-wide statistics (total blocks, transactions, addresses, gas price, etc). GET /stats
- Get token
Get info about a token (ERC-20/721/1155) by contract address. GET /tokens/{address_hash}
- Get token instance
Get detailed info about a specific NFT instance. GET /tokens/{address_hash}/instances/{id}
- Get transaction
Get detailed information about a specific transaction by hash. GET /transactions/{transaction_hash}
- List address NFTs
List NFTs owned by a specific address. GET /addresses/{address_hash}/nft
- List address token balances
List all token balances held by a specific address. GET /addresses/{address_hash}/token-balances
- List address token transfers
List token transfers involving a specific address. GET /addresses/{address_hash}/token-transfers
- List address transactions
List transactions involving a specific address. GET /addresses/{address_hash}/transactions
- List blocks
List recent blocks on the chain. GET /blocks
- List smart contracts
List verified smart contracts. GET /smart-contracts
- List token holders
List holders of a given token. GET /tokens/{address_hash}/holders
- List token transfers
List transfers of a given token. GET /tokens/{address_hash}/transfers
- List transactions
List recent transactions on the chain. GET /transactions
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