Infrastructure optimized for growth
100+
Networks Supported
25ms
Avg Processing Time
25,000+ rq/s
Enterprise-ready
100+ TB
of Big Data
Access to full transaction data on all transactions & addresses
Broadcast and verify transactions with real-time monitoring
Retrieve blockchain data, balances, and transactions
Detailed blockchain history and transaction data for any address.
Full smart contracts metadata, including token symbols & token names
Dedicated nodes infrastructure for leading blockchains using JSON-RPC
Address validation, encoding & cryptographic tasks optimizations
Shared node infrastructure for top blockchains using JSON-RPC.
Pay for HTTP APIs, or charge for your own, in USDC stablecoin over the open x402 protocol — non-custodial, on-chain settlement.
Real-time notifications for events on top blockchains. Response under 100ms.
AML address screening across 20+ blockchains
14 MCP servers + n8n MCP client for AI agents
Precise blockchain transaction fee estimates based on transaction priority
Sync and manage HD wallets, keys and addresses
Prepare EVM transactions, including token transfers
Access to full transaction data on all transactions & addresses
Get live crypto prices, exchange rates, supply and token contracts across protocols via one REST API.
Test EVM transactions, optimize gas fees and identify security flaws
The U.S. Securities and Exchange Commission (SEC) has proposed a new framework for token offerings, including an exemption for raises up to 75 million dollars. For teams building tokenized securities and stablecoin payment rails, this proposal shapes how issuance workflows must integrate AML screening and address verification. Regulatory clarity here changes the compliance surface developers have to build against.
The SEC introduced draft rules that would create a tailored exemption for token offerings raising up to 75 million dollars over a 12-month period. The framework aims to give issuers a defined path to distribute tokens without the full registration burden that applies to traditional securities offerings. Anti-Money Laundering (AML) obligations, investor disclosures, and conditions on secondary transfers sit at the center of the proposal.
This follows a broader shift at the agency toward on-chain financial products. The SEC recently cleared the Franklin OnChain U.S. Government Money Fund as cash and collateral, signaling growing acceptance of tokenized instruments settling on public chains. The token offering proposal extends that direction into primary issuance. Under the draft, issuers claiming the exemption would still need to screen participants and monitor token movement to satisfy Bank Secrecy Act (BSA) and Financial Crimes Enforcement Network (FinCEN) expectations.
A 75 million dollar exemption lowers the cost of compliant token issuance for SMEs and mid-market issuers. That expands the pool of teams launching tokenized securities, and each of them inherits an AML and Know Your Customer (KYC) obligation at the moment of distribution. The compliance requirement does not disappear with the exemption. It moves into the issuance pipeline itself.
For developers, the practical question is where screening happens. A token sale distributes assets to wallet addresses. Before those addresses receive tokens, issuers need to confirm the recipient is not on a sanctions list and does not carry exposure to illicit activity. This is address-level screening, and it has to run at the pace of on-chain settlement. Our Verify Address product screens addresses against AML and sanctions data across 20+ chains, which lets issuance systems gate distribution programmatically rather than through manual review.
The proposal also matters because it defines conditions on secondary transfers. Tokens sold under the exemption may carry transfer restrictions. Enforcing those restrictions requires monitoring where tokens go after issuance. That is a continuous obligation, not a point-in-time check at sale.
Teams building token issuance platforms should treat AML screening as an inline step, not a downstream report. Three areas need attention.
First, pre-distribution screening. Every recipient address should be verified before it receives tokens. This means calling an address verification service during the offering workflow and blocking distribution to flagged addresses. Building this into the issuance smart contract logic or the distribution backend keeps the process auditable and repeatable across offerings.
Second, post-issuance monitoring. Transfer restrictions and ongoing AML duties require visibility into token movement. Webhook infrastructure that fires on address activity gives compliance teams real-time signals when a restricted token moves. Our Blockchain Events product delivers these notifications with sub-100ms response times, so monitoring keeps pace with settlement across Ethereum, Solana, and other supported chains. For a practical implementation pattern, see our guide on monitoring blockchain addresses with webhooks.
Third, transaction validation before broadcast. Issuers distributing at scale need to confirm that a transaction will execute as intended before committing it on-chain. Simulating distribution transactions surfaces failures and unexpected state changes before gas is spent. This reduces failed settlements during large offerings and gives compliance a chance to intercept problematic transfers.
The overlap with stablecoin payment rails is direct. Many issuers settling tokenized securities also handle stablecoin flows for subscriptions and redemptions. The same AML screening and address verification apply. Fidelity's dollar stablecoin entering DeFi and Mastercard's crypto credential work both point to the same requirement: institutional-grade screening embedded in the payment path. Issuers cannot run separate compliance stacks for securities and stablecoins. A unified address verification layer across both keeps the operation coherent.
The proposal is a draft. A public comment period will follow, and the final rule may adjust the exemption threshold, the AML conditions, or the transfer restrictions. Developers should track the comment period closely because the technical requirements for screening and monitoring depend on the final language.
Watch how the SEC coordinates with FinCEN on BSA obligations for exempt offerings. If the final rule specifies screening frequency or data standards, issuance platforms will need to match those standards in their verification calls. Also watch how state regulators respond, since token offerings often touch multiple U.S. jurisdictions.
Internationally, the contrast with the Markets in Crypto-Assets (MiCA) regime in the European Union matters. Teams operating across the U.S. and EU will run two compliance frameworks. Address screening across 20+ chains gives a common technical foundation, but the rule logic differs by jurisdiction. Building configurable compliance gates rather than hardcoded checks keeps issuance systems adaptable as both frameworks finalize.
Finally, watch adoption. If the 75 million dollar exemption draws issuers, the volume of tokenized securities distributions will grow. That raises the throughput demands on screening and monitoring infrastructure. Systems that handle a handful of offerings need to scale to hundreds without degrading response time.
If you are building token issuance or stablecoin payment infrastructure that has to meet these requirements, our product suite covers address verification, real-time event monitoring, and transaction simulation across 20+ chains. You can start on the free tier with no credit card required and test the screening and webhook flows against your issuance pipeline.
Networks Supported
Avg Processing Time
Enterprise-ready
of Big Data