by Script Master Labs LLC

OMNIGATE review, pricing and limits

x402 gateway for agents: find paid APIs, vet a spend, run budgeted scripts

Best for
Agent developer
Not for
Compliance officer needing a regulated payment provider
  • App connectors
  • Data

Should you use OMNIGATE?

Worth connecting to read the payment contract and try the free discovery tools. Be careful with paid tools until the vendor reconciles its docs and live prices, because the two disagree. The npm package alone is only discovery, and the paid tools live on the hosted endpoint.

One MCP surface that covers discovery, spend vetting and budgeted script execution, all settled per call in USDC with no account.

Also for

  • Agent-commerce builder
  • Agent developers adding pay-per-call APIs to an MCP client
Show 2 more
  • Builders of x402 servers who want to be listed in directories
  • Quantitative researchers experimenting with signal-coherence checks

Main trade-off

Prices that differ between the docs and the live tool list, with market-data tools sharing one server with the payment tools.

OMNIGATE pricing

Free tools for discovery, status, contract, runtime search, report read-back and receipts. Everything else is paid per call in USDC on Base, with prices quoted in the payment challenge. The npm package is MIT licensed.

Billing model
Usage

Install OMNIGATE

npx @scriptmasterlabs/mcp-x402

Before you start

  • Node 20 or later to run the npm package locally
  • Or an MCP client that can connect to https://mcp-x402.onrender.com/mcp over streamable HTTP
  • A wallet able to authorize x402 v2 USDC payments on Base for the paid tools

How to invoke it

Exposed as MCP tools over streamable HTTP; the agent initializes a session, lists tools and calls them by name, and paid tools return an HTTP 402 challenge to authorize.

Works with

  • Any MCP client with streamable HTTP support

Data it can reach

  • x402 paid-route catalog
  • US stock and ETF market data
  • run receipts

The permissions this connector asks for, as its own documentation states them.

What OMNIGATE can do

14 actions an agent can call. Open one for its parameters and an example.

Discover SML x402 GatewayFree, read-only call that returns the gateway's job, transport and canonical x402 payment contract, and where to read fresh per-route payment requirements.

Example call

{"name":"sml_discover","arguments":{}}
Inspect SML Gateway StatusFree, read-only call that returns gateway readiness, the active tool profile and the names of the registered gateway tools.

Example call

{"name":"sml_status","arguments":{}}
Inspect x402 ContractFree call that returns the payment network, USDC asset, payTo address, payment headers and the rule for resolving a target's fresh requirements.

Example call

{"name":"x402_contract","arguments":{}}
Score Signal Coherence: Coherent GatePaid call that scores whether trading-signal paths agree and returns a confidence-weighted consensus, a 0 to 1 coherence value and a pass or block gate.

Example call

{"name":"interfere","arguments":{"paths":[{"source":"momentum","direction":"long","confidence":0.7},{"source":"mean-reversion","direction":"flat","confidence":0.4}]}}

Parameters

ParameterTypeNeededDescription
pathsarrayOptionalSignal paths to check, each with a source, direction and confidence.
tickerstringOptionalOptional: pull extra paths for this ticker from registered path sources (see docs/COHERENT_GATE_PATH_SOURCES.md).
sourcesarrayOptionalPath-source ids to pull for the ticker; needs a ticker.
wallet_addressstringOptionalinterfere: your wallet address.
payment_tx_hashstringOptionalinterfere: Base USDC payment hash.
payment_headerstringOptionalinterfere: base64 x402 payment payload.
arc_auth_idstringOptionalinterfere: Arc escrow authorization id.
Score Coherence with Leviathan SignalPaid call that fetches the vendor's Leviathan signal for a ticker, adds it as one path and runs the same coherence gate.

Example call

{"name":"leviathan_interfere","arguments":{"ticker":"AAPL","signal_type":"squeeze"}}

Parameters

ParameterTypeNeededDescription
tickerstringRequiredTicker symbol, 1-10 uppercase letters (e.g. AAPL).
signal_typestringRequiredWhich Leviathan signal to fetch and add as a path: squeeze, momentum, or all.
pathsarrayOptionalExtra signal paths added to the Leviathan one, 32 in total at most.
sourcesarrayOptionalExtra path-source ids added beside the Leviathan signal.
wallet_addressstringOptionalleviathan_interfere: your wallet address.
payment_tx_hashstringOptionalleviathan_interfere: Base USDC payment hash.
payment_headerstringOptionalleviathan_interfere: base64 x402 payment payload.
arc_auth_idstringOptionalleviathan_interfere: Arc escrow authorization id.
Check Before an Agent Wallet Pays: Spend GatePaid advisory check in which four inputs vote on whether an agent wallet should pay a payee a quoted amount; it moves no funds.

Example call

{"name":"spend_gate_check","arguments":{"payee":"api.example.com","quoted_amount":0.05,"tool_category":"market_data"}}

Parameters

ParameterTypeNeededDescription
payeestringRequiredPayee domain (e.g. "api.example.com") and/or full endpoint URL the wallet is about to pay.
quoted_amountnumberRequiredQuoted amount in USDC the wallet is about to pay.
tool_categorystringOptionalOptional category of the tool/service being bought (e.g. data_lookup, market_data, inference, compute). Selects the v1 default cap when policy_cap_usdc is omitted; when omitted entirely the cap table's "default" cap applies.
policy_cap_usdcnumberOptionalOptional caller policy cap in USDC; overrides the v1 default cap table for price_sanity.
manifest_urlstringOptionalOptional package page URL (npmjs.com/package/…, pypi.org/project/…, crates.io/crates/…) for the payload_safety path.
wallet_addressstringOptionalspend_gate_check: your wallet address.
payment_tx_hashstringOptionalspend_gate_check: Base USDC payment hash.
payment_headerstringOptionalspend_gate_check: base64 x402 payment payload.
Where Will the 11/64 EMA Cross?: SML PRECROSSPaid analysis that returns the price at which the 11 and 64 EMA cross on the next bar for a US stock or ETF, with a walk-forward self-backtest.

Example call

{"name":"precross_analyze","arguments":{"timeframe":"1d","symbol":"SPY"}}

Parameters

ParameterTypeNeededDescription
timeframestringdefault 4hOptional1h or 4h (regular-session bars) or 1d.
symbolstringRequiredTicker to analyse, for example AMC or GME.
wallet_addressstringOptionalprecross_analyze: your wallet address.
payment_tx_hashstringOptionalprecross_analyze: Base USDC payment hash.
payment_headerstringOptionalprecross_analyze: base64 x402 payment payload.
Which US Stocks Have Aligned Technicals Today?: SML REGIME SCANPaid scan of liquid US stocks and ETFs that reads the market regime first and returns ranked setups with trigger and invalidation levels.

Example call

{"name":"regime_scan_board","arguments":{"bias":"bullish","limit":10}}

Parameters

ParameterTypeNeededDescription
biasstringOptionalOnly return setups with this bias.
setupstringOptionalOnly return this setup type.
limitintegerOptionalMax tickers (default all, up to 25).
include_familiesbooleanOptionalInclude the 8 family readings and missing checks per ticker (longer answer).
wallet_addressstringOptionalregime_scan_board: your wallet address.
payment_tx_hashstringOptionalregime_scan_board: Base USDC payment hash.
payment_headerstringOptionalregime_scan_board: base64 x402 payment payload.
Show all 14 actions
Regime + One-Per-Family Read for One Ticker: SML REGIME SCANPaid single-ticker reading from the same regime engine, for any US stock or ETF whether or not it is on the board.

Example call

{"name":"regime_scan_ticker","arguments":{"symbol":"NVDA"}}

Parameters

ParameterTypeNeededDescription
symbolstringRequiredUS stock or ETF ticker, such as NVDA or SPY.
wallet_addressstringOptionalregime_scan_ticker: your wallet address.
payment_tx_hashstringOptionalregime_scan_ticker: Base USDC payment hash.
payment_headerstringOptionalregime_scan_ticker: base64 x402 payment payload.
File Once, List to All: OmniListPaid run that checks one x402 or MCP server record against several directories, files it where it is missing and reads back receipts.

Example call

{"name":"omnilist_run","arguments":{"name":"My MCP Server","kind":"mcp-server","description":"Remote MCP server that returns weather forecasts to agents.","mcp_endpoint":"https://example.com/mcp","contact_email":"ops@example.com"}}

Parameters

ParameterTypeNeededDescription
namestringRequiredServer name, e.g. "OMNIGATE".
kindstringRequiredWhat the record describes.
descriptionstringRequiredOne-paragraph description; the first sentence is load-bearing.
mcp_endpointstringOptionalRemote MCP endpoint (streamable-http), when the server speaks MCP.
api_base_urlstringOptionalBase URL of the x402 API surface, for plain HTTP APIs.
endpointsarrayOptionalIndividual payable endpoint URLs for endpoint-level venues (402index, x402dash).
websitestringOptionalWebsite / product page URL.
contact_emailstringRequiredContact email filings are made under (x402-list gates one filing per email per 7 days).
networksarrayOptionalNetwork slugs the server settles on, e.g. ["base"].
settler_addressesarrayOptionalSettler / signer addresses (facilitators).
settler_addressstringOptionalSingle settler / signer address (facilitators): alias for a one-entry settler_addresses list.
facilitator_slugstringOptionalFacilitator slug on x402-list (lowercase letters, digits, hyphens): required for x402-list facilitator filings.
registry_namestringOptionalMCP Registry name you own, e.g. "com.example/my-server": used for the PREPARED server.json artifact.
toolsarrayOptionalTool inventory for the MCP Registry artifact: every tool name + price is declared in the generated server.json.
wallet_addressstringOptionalomnilist_run: your wallet address.
payment_tx_hashstringOptionalomnilist_run: Base USDC payment hash.
payment_headerstringOptionalomnilist_run: base64 x402 payment payload.
OmniList Run ReportFree read-back of the per-venue states and receipts of an earlier OmniList run.

Example call

{"name":"omnilist_report","arguments":{"run_id":"$RUN_ID"}}

Parameters

ParameterTypeNeededDescription
run_idstringRequiredRun id returned by omnilist_run.
formatstringOptionalReport format; default json.
Search the OMNIGATE Runtime catalogFree search of the paid routes and published capsules that a runtime script can call, with their live prices.

Example call

{"name":"omnigate_runtime_search","arguments":{"query":"short squeeze","limit":5}}

Parameters

ParameterTypeNeededDescription
querystringOptionalKeywords, e.g. "short squeeze", "sec filings", "web extract". Empty lists everything (capped).
limitintegerdefault 20OptionalMax routes to return.
Run a paid multi-tool script: OMNIGATE RuntimePaid run of one JavaScript script in a sandbox that calls many routes in one round trip under a hard USDC budget.

Example call

{"name":"omnigate_runtime_execute","arguments":{"script":"const hits = await sml.tools.search('short squeeze'); return hits;","budget_usdc":"0.05","mode":"sync"}}

Parameters

ParameterTypeNeededDescription
scriptstringOptionalJavaScript async-function body. Use await; return the final result.
capsule_idstringOptionalRun a published capsule instead of a script (e.g. cap_name@1 or cap_name@latest).
budget_usdcstringdefault 0.05OptionalHard spending cap for the whole run in USDC (min 0.01, max 25).
inputobjectOptionalJSON object exposed to the script as sml.input.
modestringdefault syncOptionalsync waits for the result (120s wall); async returns run_id to poll /runtime/runs/{id}.
payment_headerstringOptionalomnigate_runtime_execute: base64 x402 payment payload.
credit_tokenstringOptionalRuntime credit token (smlrt_…) returned by an earlier run.
arc_auth_idstringOptionalomnigate_runtime_execute: Arc escrow authorization id.
Get and verify an OMNIGATE Runtime receiptFree fetch and verification of a signed, hash-chained receipt for a runtime run.

Example call

{"name":"omnigate_runtime_receipt","arguments":{"receipt_id":"$RECEIPT_ID"}}

Parameters

ParameterTypeNeededDescription
receipt_idstringRequiredReceipt id from a runtime run (rcpt_…).

What OMNIGATE is for

A remote MCP server and x402 facilitator from Script Master Labs that gives an agent 14 public tools to discover pay-per-call APIs, check a payee before paying and run budgeted scripts. Free tools handle discovery, and paid tools answer with an HTTP 402 challenge settled in USDC on Base or Arc.

  • Discovery and status tools

    Free read-only tools return the gateway contract, readiness, the registered tool names and the canonical payment rail.

  • Spend gate

    An advisory check in which four inputs vote pay-side or reject-side, requires coherence of at least 0.6 and moves no funds.

  • Budgeted script runtime

    One sandboxed JavaScript run calls many routes under a hard USDC cap, charges only upstream 2xx answers and returns unused budget as a credit token.

  • Signed receipts

    Every runtime run produces an Ed25519-signed, hash-chained receipt that can be fetched and verified for free.

Show all 6 features
  • Market-data tools

    Ranked US stock setups, an EMA-cross price and a signal coherence gate come as tools that the vendor labels research, not advice.

  • OmniList filing

    One call checks an x402 or MCP server across five directories and a registry artifact, then returns a per-venue report.

What people use it for

  • Vet a payee before an agent wallet pays

    An agent calls the spend gate with the payee and quoted amount and gets a pay-side or reject-side verdict before any money moves.

  • Run many paid API calls under one budget

    An agent sends one script to the runtime with a hard USDC cap instead of making one model round trip per paid call, and keeps a signed receipt.

  • File an x402 or MCP server into several directories

    A builder gives one server record to OmniList and reads back a per-venue report of what was filed, pending or already present.

  • Shortlist liquid US tickers whose technicals agree

    A research agent asks the regime scan for ranked setups with trigger and invalidation levels, then reads one ticker in detail.

Strengths and limits

Strengths

  • Free read-only tools let an agent inspect the payment contract and the catalog before it commits any money.
  • The docs state that the caller controls payment authorization and that the gateway does not autonomously spend.
  • The runtime caps a run with a hard budget and charges only for upstream calls that answer 2xx, which limits what a runaway script can cost.
  • The live MCP server answers the standard protocol and lists its own tools, so the action list on this page can be checked against it.

Limits

  • The vendor's own pages disagree on prices: the docs quote the spend gate at 0.005 USDC and the EMA-cross tool at 0.02 USDC, while the live tool list read on 17 November 2026 quotes 0.001 for both.
  • The largest tier of the coherence gate is charged upfront and, per its tool description, the unused difference is recorded as owed and not yet refunded automatically on the standard rail.
  • The npm package is described as read-only discovery, while the paid tools exist only on the hosted endpoint, so installing the package alone does not give an agent the paid tools.
  • The live server lists 15 tools, and its own description of one calls it an owner-only private feed that needs an access key and is not for agents.

OMNIGATE alternatives

SkillWorks withConnects byChecked
OMNIGATE This page--MCP17 Nov
Link Agent WalletPick Link Agent Wallet if an agent should buy from regular web shops using credentials you approve; pick OMNIGATE when the seller speaks x402 and the agent pays in USDC per call.ClaudeMCP25 Oct
Personal Agent ProtocolOpen standard for how personal AI agents sign in and act for customers.--Skill file27 Oct
AgentCardLet your AI agent pay online with a card it never sees, from the user's Vault or newly issuedClaude · ChatGPT · Cursor · WindsurfMCP25 Oct

OMNIGATE facts

Protocol
MCP
Authentication
Custom
Latency class
Moderate
Open source
Yes
Rate limits
The facilitator fee is waived inside a daily budget of 500 settlements across all payees and 100 per payee, counted per UTC day; past it a fee-less payment is refused until the next UTC day. A synchronous runtime run waits up to 120 seconds.

What changed

  • New feature Gateway docs refreshed with Runtime, Spend Gate, Regime Scan and PRECROSS source
  • Release @scriptmasterlabs/mcp-x402 2.1.11 published on npm source

Questions about OMNIGATE

What does OMNIGATE cost to use?

Discovery, status, the payment contract, runtime search, report read-back and receipts are free. Paid tools bill per call in USDC on Base: the live tool list quotes 0.001 for the spend gate and the EMA-cross tool, 0.02 and 0.05 for the single-ticker and board regime scans, 0.01, 0.05 or 0.25 for the coherence gate by path count and 1.00 for OmniList. The runtime sets a budget between 0.01 and 25 and adds a 0.002 platform fee per run, and the vendor's docs quote some of these prices differently.

Is OMNIGATE free or open source?

The npm package is MIT licensed, needs Node 20 or later and is described as read-only discovery. The hosted endpoint is a paid service for everything beyond the free tools, and the vendor points to a GitLab repository as its current source.

Which agents and clients can use OMNIGATE?

Any MCP client that supports streamable HTTP can connect to the hosted endpoint, since it answers the standard initialize and tools/list calls. The docs name no specific assistants, so test your own client with the free tools before you wire in a wallet.

Why does tools/list fail with Server not initialized?

When read on 17 November 2026, a tools/list call sent before the initialize handshake returned error code -32000 with the message Server not initialized. Send initialize first, keep the session id the server returns, send the initialized notification, and then list tools in the same session.

Can OMNIGATE spend my money without asking?

According to the docs, authorization sits with the caller, and the gateway never spends autonomously. A paid tool returns a payment challenge, and the agent submits a signature only when its own policy allows it. A challenge or signature is not proof of settlement, which the docs say to confirm from settlement evidence.

About OMNIGATE

OMNIGATE is the gateway side of the x402 stack from Script Master Labs LLC, a US company that describes itself as a service-disabled veteran-owned small business and also makes the ClaimGate fact-checking skill and ScriptMaster SEO Command. It is a skill and not a standalone tool because an agent reaches it only by calling MCP tools: it adds the abilities to find pay-per-call APIs, check a payee ahead of a payment, and run many paid calls under one budget. The npm package behind it was created on 19 June 2026 and its latest release, 2.1.11, was published on 9 September 2026.

Read the full background

An agent connects to the remote MCP endpoint over streamable HTTP, completes the standard initialize handshake and then lists or calls tools. Free tools cover discovery, status, the payment contract, runtime search and receipts. A paid tool replies with a 402 payment challenge; the caller decides whether to authorize USDC on Base or Arc, and the docs say the gateway never spends on its own. A sandboxed runtime lets one script call several routes and returns an Ed25519-signed, hash-chained receipt.

Any MCP client that speaks streamable HTTP can use it, and the same server also exposes market-data tools (a regime scan, an EMA-cross analysis and a signal coherence gate) that the vendor labels research output and not financial advice. It fits agent-commerce builders who want a spend check before a wallet pays, and teams listing an x402 server in several directories at once.

Do not choose it if you need one predictable price per tool: the vendor's docs and its live tool list quote different prices for the same tools, and the top price tier of the coherence gate is billed upfront with no automatic refund of the unused part. An agent that simply needs to pay ordinary online merchants with credentials you approve suits Link Agent Wallet. It is filed under integration skills.

The gateway's llms.txt, marked as refreshed on 4 November 2026, documents the runtime, the spend gate, the regime scan and the EMA-cross tools, and the vendor states that on 2 November 2026 fifteen of its own services were paid end to end through OMNIGATE and settled on Base, a self-proof it labels as such.

Sources and guides

More Agent Skills on Hokai

  • NVIDIA BioNeMo Agent ToolkitAgent-callable skills for protein folding, docking, and genomics on NVIDIA NIM
  • find-skillSearch and install skills from the Orthogonal library for agents.
  • DiditIdentity verification, KYB, AML and transaction monitoring an agent can configure and run over a hosted MCP server.
  • ComposioOne MCP endpoint that lets an agent act in 1,500+ apps with managed auth.
  • Pipedrive MCP ServerConnect Claude, ChatGPT and Cursor to your Pipedrive CRM with no code