onchainpulse

OnchainPulse: Intelligence API for the onchain financial transition. Decodes legislation, tracks RWA tokenization, models sector scenarios, guides onchain integration. All endpoints require x402 payment (USDC on Ba Coverage: Global Endpoints: • legislation ($0.15): Legislative intelligence — plai...

Server Pulsenetwork https://pulse.theaslangroupllc.com/api/mcp
Category Financial
Risk class Critical
Parameters 120 required

What onchainpulse does on Pulsenetwork

AI agents use onchainpulse to commit financial operations through Pulsenetwork — usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
q string Bill name or topic (e.g. 'GENIUS Act', 'stablecoin regulation', 'MiCA')
lang string Response language (ISO 639-1 code)
mint string SPL token mint address (base58)
risk string Risk tolerance for recommendations framing
term string Term to explain (e.g. 'atomic settlement', 'MiCA', 'CASP', 'yield bearing stablecoin', 'RWA')
type string Type of transition
asset string Which ETF complex to analyze
chain string EVM chain (default base)
scope string scope
topic string topic
action string Type of analysis
period string period

Parameters from the server's own tool schema.

Why onchainpulse needs a policy

Every invocation of this tool commits a financial transaction — spending USDC on Base per query. The tool is explicitly designed around a pay-per-use financial model, making each call a real monetary obligation. An AI agent autonomously invoking this tool repeatedly could accumulate significant financial costs, placing it firmly in the Financial category with high severity.

From the tool's definition All endpoints require x402 payment (USDC on Base); per-query costs of $0.10–$0.20 USDC; tracks RWA tokenization and onchain financial transition; agents pay per query via x402 USDC on Base

Risk signalsHigh parameter count (23 properties)

Questions about onchainpulse

What does the onchainpulse tool do? +

OnchainPulse: Intelligence API for the onchain financial transition. Decodes legislation, tracks RWA tokenization, models sector scenarios, guides onchain integration. All endpoints require x402 payment (USDC on Ba Coverage: Global Endpoints: • legislation ($0.15): Legislative intelligence — plain English bill translation with sector impact • rwa ($0.15): Real world asset market overview — top-of-funnel scan across asset classes • scenario ($0.20): Sector impact scenario modeling — if/then structural analysis • transition ($0.10): Onchain transition guide — practical onboarding by type • monitor ($0.10): Institutional onchain activity monitor — weekly/monthly brief • compliance ($0.15): Regulatory compliance intelligence — jurisdiction-specific framework guidance • tokenize ($0.15): Tokenization intelligence — how to tokenize any asset type • yield ($0.25): Tokenized yield intelligence — live rates and risk-adjusted comparison • glossary ($0.05): Plain English decoder — any onchain finance or regulatory term • snapshot ($0.10): State of the transition — weekly/monthly macro brief • memecoin ($0.015): Solana memecoin pre-trade safety + momentum verdict (deterministic, no-LLM) • evmtoken ($0.015): EVM memecoin pre-trade safety + momentum verdict (deterministic, no-LLM, multi-chain) • rwa-yield ($0.20): Tokenized-treasury/MMF yield comparison — BUIDL, USDY, OUSG, USYC, USTB, BENJI • rwa-risk ($0.25): RWA issuer and redemption risk read for a named product • gold-check ($0.15): Tokenized gold comparison — PAXG vs XAUT • etf-flows ($0.15): Crypto ETF flow intelligence — US spot BTC/ETH/SOL, per-issuer breakdown • clarity-watch ($0.10): CLARITY Act tracker — live congress.gov status, CFTC/SEC split, passage odds. It is categorised as a Financial tool in the Pulsenetwork MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does onchainpulse accept? +

onchainpulse accepts 12 parameters: q, lang, mint, risk, term, type, asset, chain, scope, topic, action, period. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on onchainpulse? +

Register the Pulsenetwork MCP server in PolicyLayer and add a rule for onchainpulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.

What risk level is onchainpulse? +

onchainpulse is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit onchainpulse? +

Yes. Add a rate_limit block to the onchainpulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block onchainpulse completely? +

Set action: deny in the PolicyLayer policy for onchainpulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides onchainpulse? +

onchainpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

onchainpulse is one line of Pulsenetwork's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.