pulsenetwork

arbipulse

ArbiPulse: The arbitrage layer for every market — 18 endpoints finding the same thing at two prices: prediction-market cross-venue spreads (Polymarket×Kalshi), GPU compute rental gaps, AI inference token pricing, stablecoin parallel-rate premiums, retail resale margins, plus DeFi yields, DEX/CEX differentials, funding rates, sports surebets, ETF/NAV gaps, commodities.

Coverage: Global

Endpoints: • scanner ($0.10): Unified Arbitrage Scanner • perps ($0.10): Perpetual Futures Funding Rate Carry • flash ($0.75): Flash Loan Strategy Builder • sports ($0.10): Sports Surebet Scanner • crypto ($0.07): CEX Spot Price Arbitrage • dex ($0.10): DEX Price Arbitrage • execute ($0.75): Execution Package Builder • calculator ($0.02): Arbitrage Profit Calculator • commodity ($0.10): Commodity Regional Arbitrage • pairs ($0.15): Statistical Arbitrage (Pairs Trading) • spread-tick ($0.02): Cross-exchange spread tick for one pair • predmarket-arb ($0.05): Prediction market cross-venue arbitrage (Polymarket × Kalshi) • compute-arb ($0.05): GPU compute price arbitrage (marketplace vs hyperscaler) • fx-premium ($0.02): Stablecoin parallel-rate premium (capital-control FX signal) • flip-check ($0.50): Retail resale arbitrage check (comps + fees + verdict) • inference-arb ($0.05): AI inference price arbitrage (same model, every provider) • flash-scan ($0.25): Flash Loan Pool Scan (lite preview)

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	H100 (default) \| H200 \| B200 \| A100 \| L40S \| RTX4090 \| RTX5090
`days`	No	days
`fiat`	No	ARS (default) \| VES \| BRL \| COP \| PEN \| MXN \| CLP \| BOB
`item`	No	Product, specific (brand + model number)
`lang`	No	Response language code (en \| es \| fr \| de \| zh \| hi \| ar \| pt \| ja \| ko \| etc.)
`pair`	No	pair
`scan`	No	Top Polymarket contracts to match (default 8, max 12)
`unit`	No	unit
`asset`	No	asset
`chain`	No	chain
`model`	No	OpenRouter slug or fuzzy name (default meta-llama/llama-3.3-70b-instruct)
`query`	No	Optional topic filter, e.g. fed \| world cup \| bitcoin
`sport`	No	sport
`token`	No	token
`action`	Yes	Which endpoint to call. Options: scanner \| perps \| flash \| sports \| crypto \| dex \| execute \| calculator \| commodity \| pairs \| spread-tick \| predmarket-arb \| compute-arb \| fx-premium \| flip-check \| inference-arb \| flash-scan
`amount`	No	amount
`chains`	No	chains
`region`	No	region
`asset_a`	No	asset_a
`asset_b`	No	asset_b
`gas_usd`	No	gas_usd
`min_apy`	No	min_apy
`regions`	No	regions
`arb_type`	No	arb_type
`category`	No	category
`platform`	No	platform
`protocol`	No	protocol
`receiver`	No	receiver
`strategy`	No	strategy
`buy_price`	No	Acquisition cost in USD
`commodity`	No	commodity
`exchanges`	No	exchanges
`ship_cost`	No	Outbound shipping estimate in USD (default 8)
`amount_usd`	No	amount_usd
`exit_price`	No	exit_price
`long_venue`	No	long_venue
`asset_class`	No	asset_class
`entry_price`	No	entry_price
`marketplace`	No	ebay (default) \| amazon \| stockx \| poshmark \| mercari
`short_venue`	No	short_venue
`slippage_bps`	No	slippage_bps
`flash_fee_bps`	No	flash_fee_bps
`lookback_days`	No	lookback_days
`taker_fee_bps`	No	taker_fee_bps
`bridge_fee_usd`	No	bridge_fee_usd
`min_profit_pct`	No	min_profit_pct
`min_profit_usd`	No	Minimum net profit per $1,000 stake
`trade_size_usd`	No	trade_size_usd
`wallet_address`	No	wallet_address
`opportunity_type`	No	opportunity_type
`withdrawal_fee_usd`	No	withdrawal_fee_usd

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: scanner | perps | flash | sports | crypto | dex | execute | calculator | commodity | pairs | spread-tick | predmarket-arb | compute-arb | fx-premium | flip-check | inference-arb"New value: +"Which endpoint to call. Options: scanner | perps | flash | sports | crypto | dex | execute | calculator | commodity | pairs | spread-tick | predmarket-arb | compute-arb | fx-premium | flip-check | inference-arb | flash-scan"

changedInput schema / properties / action / enum

Previous value: -[
-  "scanner",
-  "perps",
-  "flash",
-  "sports",
-  "crypto",
-  "dex",
-  "execute",
-  "calculator",
-  "commodity",
-  "pairs",
-  "spread-tick",
-  "predmarket-arb",
-  "compute-arb",
-  "fx-premium",
-  "flip-check",
-  "inference-arb"
-]New value: +[
+  "scanner",
+  "perps",
+  "flash",
+  "sports",
+  "crypto",
+  "dex",
+  "execute",
+  "calculator",
+  "commodity",
+  "pairs",
+  "spread-tick",
+  "predmarket-arb",
+  "compute-arb",
+  "fx-premium",
+  "flip-check",
+  "inference-arb",
+  "flash-scan"
+]

Changed6 schema fields changedJul 14, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: scanner | defi | perps | flash | sports | crypto | dex | execute | calculator | etf | commodity | pairs | spread-tick | predmarket-arb | compute-arb | fx-premium | flip-check | inference-arb"New value: +"Which endpoint to call. Options: scanner | perps | flash | sports | crypto | dex | execute | calculator | commodity | pairs | spread-tick | predmarket-arb | compute-arb | fx-premium | flip-check | inference-arb"

changedInput schema / properties / action / enum

Previous value: -[
-  "scanner",
-  "defi",
-  "perps",
-  "flash",
-  "sports",
-  "crypto",
-  "dex",
-  "execute",
-  "calculator",
-  "etf",
-  "commodity",
-  "pairs",
-  "spread-tick",
-  "predmarket-arb",
-  "compute-arb",
-  "fx-premium",
-  "flip-check",
-  "inference-arb"
-]New value: +[
+  "scanner",
+  "perps",
+  "flash",
+  "sports",
+  "crypto",
+  "dex",
+  "execute",
+  "calculator",
+  "commodity",
+  "pairs",
+  "spread-tick",
+  "predmarket-arb",
+  "compute-arb",
+  "fx-premium",
+  "flip-check",
+  "inference-arb"
+]

removedInput schema / properties / min_spread_bps

Removed value: -{
-  "description": "min_spread_bps",
-  "type": "string"
-}

removedInput schema / properties / stablecoin_only

Removed value: -{
-  "description": "stablecoin_only",
-  "type": "string"
-}

removedInput schema / properties / ticker

Removed value: -{
-  "description": "ticker",
-  "type": "string"
-}

removedInput schema / properties / type

Removed value: -{
-  "description": "type",
-  "type": "string"
-}

Changed11 schema fields changedJul 11, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: scanner | defi | perps | flash | sports | crypto | dex | execute | calculator | etf | commodity | pairs | spread-tick"New value: +"Which endpoint to call. Options: scanner | defi | perps | flash | sports | crypto | dex | execute | calculator | etf | commodity | pairs | spread-tick | predmarket-arb | compute-arb | fx-premium | flip-check | inference-arb"

changedInput schema / properties / action / enum

Previous value: -[
-  "scanner",
-  "defi",
-  "perps",
-  "flash",
-  "sports",
-  "crypto",
-  "dex",
-  "execute",
-  "calculator",
-  "etf",
-  "commodity",
-  "pairs",
-  "spread-tick"
-]New value: +[
+  "scanner",
+  "defi",
+  "perps",
+  "flash",
+  "sports",
+  "crypto",
+  "dex",
+  "execute",
+  "calculator",
+  "etf",
+  "commodity",
+  "pairs",
+  "spread-tick",
+  "predmarket-arb",
+  "compute-arb",
+  "fx-premium",
+  "flip-check",
+  "inference-arb"
+]

addedInput schema / properties / buy_price

Added value: +{
+  "description": "Acquisition cost in USD",
+  "type": "string"
+}

addedInput schema / properties / fiat

Added value: +{
+  "description": "ARS (default) | VES | BRL | COP | PEN | MXN | CLP | BOB",
+  "type": "string"
+}

addedInput schema / properties / gpu

Added value: +{
+  "description": "H100 (default) | H200 | B200 | A100 | L40S | RTX4090 | RTX5090",
+  "type": "string"
+}

addedInput schema / properties / item

Added value: +{
+  "description": "Product, specific (brand + model number)",
+  "type": "string"
+}

addedInput schema / properties / marketplace

Added value: +{
+  "description": "ebay (default) | amazon | stockx | poshmark | mercari",
+  "type": "string"
+}

addedInput schema / properties / model

Added value: +{
+  "description": "OpenRouter slug or fuzzy name (default meta-llama/llama-3.3-70b-instruct)",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Optional topic filter, e.g. fed | world cup | bitcoin",
+  "type": "string"
+}

addedInput schema / properties / scan

Added value: +{
+  "description": "Top Polymarket contracts to match (default 8, max 12)",
+  "type": "string"
+}

addedInput schema / properties / ship_cost

Added value: +{
+  "description": "Outbound shipping estimate in USD (default 8)",
+  "type": "string"
+}

Changed2 schema fields changedJul 9, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: scanner | defi | perps | flash | sports | crypto | dex | execute | calculator | etf | commodity | pairs"New value: +"Which endpoint to call. Options: scanner | defi | perps | flash | sports | crypto | dex | execute | calculator | etf | commodity | pairs | spread-tick"

changedInput schema / properties / action / enum

Previous value: -[
-  "scanner",
-  "defi",
-  "perps",
-  "flash",
-  "sports",
-  "crypto",
-  "dex",
-  "execute",
-  "calculator",
-  "etf",
-  "commodity",
-  "pairs"
-]New value: +[
+  "scanner",
+  "defi",
+  "perps",
+  "flash",
+  "sports",
+  "crypto",
+  "dex",
+  "execute",
+  "calculator",
+  "etf",
+  "commodity",
+  "pairs",
+  "spread-tick"
+]

First observedJul 6, 2026

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, but it only discloses endpoint names and per-call prices. It doesn't disclose whether endpoints return data, execute trades, require authentication, or have side effects. Potentially sensitive endpoints like 'execute' and 'flash' receive no safety explanation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a front-loaded summary, coverage line, and a bulleted endpoint list with prices. It is somewhat long but necessary for a multi-endpoint tool. Minor inconsistency: it claims '18 endpoints' but lists 17.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the long endpoint list, the description lacks operational context for a complex 51-parameter tool: it doesn't explain which parameters are required per endpoint, what the outputs look like, or what execution-related endpoints actually do. No output schema and no annotations make this gap significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description's endpoint list adds context for the action enum but doesn't map specific parameters to endpoints. Most parameter descriptions in the schema are terse (e.g., 'pair', 'unit'), so the endpoint list helps identify relevant parameters but does not fully compensate for the lack of usage details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies ArbiPulse as an arbitrage-focused tool ('finding the same thing at two prices') and enumerates 17 distinct endpoints with their market coverage (prediction markets, GPU compute, AI inference, etc.). This strongly distinguishes it from sibling pulse tools by domain and purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the endpoint list (e.g., sports surebets, prediction-market arbitrage) but gives no explicit when-to-use vs alternatives or when-to-avoid. It names many use cases but doesn't provide guidance on selecting among endpoints or comparing to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pulsenetwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

arbipulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources