Chain So SoChain Dogecoin Blockchain API
Agent-ready OpenAPI document · curated by JenticFinanceBankingapiKey12 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read Dogecoin balances, transactions, unspent outputs, and block data, validate addresses, and look up historical DOGE price points without running a node.
Use for: I need to check the balance of a Dogecoin address, Get the recent transactions for a Dogecoin wallet, List the unspent outputs I can use to build a new Dogecoin transaction, Look up a specific Dogecoin transaction by its hash
Not supported: Does not broadcast new transactions, manage private keys, or cover non-Dogecoin chains - use for read-only Dogecoin (DOGE and DOGETEST) chain data and DOGE price lookups only.
Jentic publishes the only available OpenAPI specification for SoChain Dogecoin Blockchain API, keeping it validated and agent-ready. The SoChain v3 API exposes read-only Dogecoin network data including address balances and summaries, transaction history, unspent outputs, block lookups, and historical DOGE price snapshots, across both mainnet (DOGE) and testnet (DOGETEST). Responses average around 5ms, which makes it suitable for live wallet UIs and on-chain analytics.
Install Jentic One Beta
Connect the SoChain Dogecoin Blockchain API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SoChain Dogecoin Blockchain API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchain.so%2Fchain-so" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchain.so%2Fchain-so" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SoChain Dogecoin Blockchain API.
Read confirmed and unconfirmed balances for a Dogecoin address
Fetch a paginated transaction history for any Dogecoin address
List unspent transaction outputs for an address to construct a new spend
Look up a single Dogecoin transaction by its hash
Retrieve a block by height or hash and fetch the latest block summary
Validate that a string is a well-formed Dogecoin mainnet or testnet address
Query historical DOGE price at a specific Unix timestamp
Use Cases
Patterns agents use SoChain Dogecoin Blockchain API for, with concrete tasks.
★ Wallet Balance Display
Show a user's Dogecoin balance and recent activity in a custodial or watch-only wallet interface. GET /balance/DOGE/{address} returns confirmed and pending balances and GET /transactions/DOGE/{address}/{page} returns paginated history. Because SoChain handles indexing, the front end avoids the cost of running and re-syncing a full Dogecoin node.
Call GET /balance/DOGE/{address} for the user's address, then GET /transactions/DOGE/{address}/1 to display the most recent page of activity
Spend Construction
Construct a new Dogecoin transaction client-side by pulling the unspent outputs for the source address. GET /unspent_outputs/DOGE/{address}/{page} returns the UTXO set the wallet can sign over, and GET /is_valid_address/DOGE/{address} confirms the destination is well-formed before any Doge moves. Used by lightweight wallets that do not embed a full node.
Call GET /unspent_outputs/DOGE/{address}/1 then call GET /is_valid_address/DOGE/{recipient} before building and broadcasting the spend
On-Chain Analytics
Aggregate Dogecoin chain data for analytics dashboards by walking blocks and pulling per-block transactions. GET /latest_blocks_summary/DOGE returns the current chain tip and recent blocks, while GET /block/DOGE/{block_hash_or_height} returns full block contents. Useful for analysts tracking miner distribution, fee trends, or large-value movements.
Call GET /best_block_hash/DOGE then GET /block/DOGE/{block_hash_or_height} for the last 100 heights and aggregate the total transaction count per block
AI Agent Crypto Lookup via Jentic
A user asks an agent 'how much DOGE is at address D... and what was DOGE worth on the day of that last incoming transaction?' Through Jentic, the agent searches for an address-balance operation, then a price-at-timestamp operation, and calls /balance/DOGE/{address} and /price/DOGE/{unix_timestamp} with credentials drawn from your Jentic One instance. The agent returns both pieces of context without any node setup.
Use Jentic to search 'get dogecoin balance' and execute it for the user's address, then search 'historical doge price' and execute /price/DOGE/{unix_timestamp} for the latest tx time
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for sochain dogecoin blockchain api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/balance/DOGE/{address}
Get confirmed and pending balance for an address
GET
/transactions/DOGE/{address}/{page}
List paginated transactions for an address
GET
/unspent_outputs/DOGE/{address}/{page}
List unspent transaction outputs for an address
GET
/transaction/DOGE/{hash}
Get a single transaction by hash
GET
/block/DOGE/{block_hash_or_height}
Get block contents by hash or height
GET
/latest_blocks_summary/DOGE
Get a summary of the latest blocks
GET
/is_valid_address/DOGE/{address}
Validate a Dogecoin address
GET
/price/DOGE/{unix_timestamp}
Get historical DOGE price at a timestamp
GET
/balance/DOGE/{address}
Get confirmed and pending balance for an address
GET
/transactions/DOGE/{address}/{page}
List paginated transactions for an address
GET
/unspent_outputs/DOGE/{address}/{page}
List unspent transaction outputs for an address
GET
/transaction/DOGE/{hash}
Get a single transaction by hash
GET
/block/DOGE/{block_hash_or_height}
Get block contents by hash or height
GET
/latest_blocks_summary/DOGE
Get a summary of the latest blocks
GET
/is_valid_address/DOGE/{address}
Validate a Dogecoin address
GET
/price/DOGE/{unix_timestamp}
Get historical DOGE price at a timestamp
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SoChain Dogecoin API by hand means handling its API-KEY header and assembling the DOGE address, transaction, and block path segments for each read yourself. Through Jentic you install once, import the SoChain Dogecoin API from the API Directory, store the key once, and your agent calls it.
Permission scoping
SoChain puts the Dogecoin address and transaction hash in the URL path for operations like /balance/DOGE/{address} and /transaction/DOGE/{hash}, so a rule can pin your agent to reads for one address. The API is read-only over Dogecoin chain data, and you choose which read operations it may call.
Credential isolation
Your SoChain API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a Dogecoin address balance' or 'list Dogecoin unspent outputs', and Jentic returns the matching SoChain operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SoChain Dogecoin Blockchain API through Jentic.
Why is there no official OpenAPI spec for SoChain Dogecoin Blockchain API?
SoChain does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SoChain Dogecoin Blockchain API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the SoChain Dogecoin API use?
The API uses an API key passed in the API-KEY request header, issued from the SoChain dashboard. Through Jentic, the key is held in your Jentic One instance and added to outgoing requests at execution time so it never enters the agent's prompt or context window.
Can I read the unspent outputs for a Dogecoin address with the SoChain API?
Yes. GET /unspent_outputs/DOGE/{address}/{page} returns the UTXO set for the given address, paginated. Wallets typically combine this with GET /is_valid_address/DOGE/{address} for the destination before constructing and signing a new spend.
What are the rate limits for the SoChain Dogecoin API?
SoChain enforces per-API-key throughput limits that vary by plan; the spec does not bake in a single number. Watch for 429 responses and the Retry-After header rather than hard-coding a fixed cadence, especially when paginating long transaction histories.
How do I check a Dogecoin balance with the SoChain API through Jentic?
Search Jentic for 'get a dogecoin address balance', load the operation backed by GET /balance/DOGE/{address}, and execute it with the address. Jentic injects the API-KEY header so the agent receives a typed balance object including confirmed and pending amounts.
Does the SoChain Dogecoin API support testnet?
Yes. The spec covers both DOGE mainnet and DOGETEST testnet network parameters via the same endpoint family. Substitute the network segment as documented for testnet workflows when you need to validate logic without spending real DOGE.
Can I limit what my agent is allowed to do with the SoChain Dogecoin API?
Yes. Because you run Jentic One yourself, your own rules decide which SoChain operations and credentials the agent may use. The API is read-only over Dogecoin chain data, and it puts the address and transaction hash directly in the URL path for calls like GET /balance/DOGE/{address} and GET /transaction/DOGE/{hash}, so you can pin the agent to reads for a single address or restrict it to specific operations such as balance and transaction lookups while blocking block or price queries.
GET STARTED