x402 Gateway (OMNIGATE)

leviathan_interfere

Coherent Gate + Leviathan (PAID, x402/USDC). Fetches the SML Leviathan signal (squeeze, momentum, or all) for a ticker, adds it as one path with your optional paths and registered sources, then runs the same coherence check as interfere: consensus, coherence 0-1, pass/block gate. Same tiers and billing as interfere ($0.25 max tier charged upfront; x402 difference recorded as owed, Arc rail captures only the used tier). If Leviathan is unavailable it continues on the other paths; with no paths it errors before charging. Max 32 paths. Not financial advice.

Input Schema

Name	Required	Description
`paths`	No	Coherent Gate: extra signal paths (Leviathan adds one; total ≤ 32).
`ticker`	Yes	Ticker symbol, 1-10 uppercase letters (e.g. AAPL).
`sources`	No	Optional path-source ids added alongside Leviathan; default = all enabled verified sources.
`arc_auth_id`	No	Arc rail: authId from AuthCaptureEscrow.authorize() for at least the max-tier amount to our receiver. Only the used tier is captured; the rest returns via reclaim() after expiry.
`signal_type`	Yes	Which Leviathan signal to fetch and add as a path: squeeze, momentum, or all.
`payment_header`	No	Base64 X-PAYMENT EIP-3009 payload (standard rail).
`wallet_address`	No	Agent wallet address (informational).
`payment_tx_hash`	No	Base USDC tx hash (sovereign rail).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

addedInput schema / properties / paths / items / properties / confidence / description
```
Added value: +"Weight 0-1 this path gets in the consensus."
```
addedInput schema / properties / paths / items / properties / direction / description
```
Added value: +"Direction this path calls: long, short, or flat."
```
addedInput schema / properties / paths / items / properties / source / description
```
Added value: +"Label for where this signal came from (1-64 chars)."
```

changedInput schema / properties / signal_type / description

Previous value: -"Leviathan engine to include as a path."New value: +"Which Leviathan signal to fetch and add as a path: squeeze, momentum, or all."

changedInput schema / properties / ticker / description

Previous value: -"Ticker symbol."New value: +"Ticker symbol, 1-10 uppercase letters (e.g. AAPL)."

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / sources

Added value: +{
+  "description": "Optional path-source ids added alongside Leviathan; default = all enabled verified sources.",
+  "items": {
+    "maxLength": 64,
+    "type": "string"
+  },
+  "maxItems": 16,
+  "type": "array"
+}

AddedOct 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With zero annotations the description carries the full burden and does so well: it discloses that it is paid (x402/USDC), the $0.25 max-tier upfront charge, how the x402 difference and Arc rail capture behave ('x402 difference recorded as owed, Arc rail captures only the used tier'), the degraded-mode behavior when Leviathan is unavailable, and that it errors before charging when there are no paths. Those billing, failure and limit details are exactly the behavioral context annotations would otherwise supply.

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?

It is front-loaded with the identity and paid nature before the operational details, and billing/failure sentences earn their place for a payment-bearing tool. It is slightly dense with billing nuance ('x402 difference recorded as owed') and repeats signal options already in the enum, keeping it just below a 5.

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

Completeness5/5

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

For an 8-parameter, paid tool with no annotations and no output schema, it covers the operational shape (consensus, coherence 0-1, pass/block gate), the payment rails, the fallback path when Leviathan is unavailable, the pre-charge error case, and the 32-path cap. Nothing essential for correct invocation is left to guesswork, and the schema fills in parameter-level detail.

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 the schema already documents ticker, signal_type enum, paths, sources, and payment fields, making 3 the baseline. The description adds only a small clarification that the 'Max 32 paths' total includes the Leviathan-added path, which explains the schema's maxItems of 31, but it introduces no syntax or semantic detail for the remaining parameters.

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?

States a specific verb and resource chain ('Fetches the SML Leviathan signal... adds it as one path... runs the same coherence check as interfere') and names the sibling 'interfere' it complements. An agent can tell exactly what this does and how it differs from interfere and sml_discover without opening a schema.

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

Usage Guidelines4/5

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

It gives clear selecting context by anchoring to 'interfere' as the baseline operation and adding the Leviathan signal path, so an agent can infer this is the version to call when it wants Leviathan plus coherence. It does not explicitly state when NOT to use it versus interfere, so it stops short of a 5.

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

All x402 Gateway (OMNIGATE) 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.

Resources

Need Help?