TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide. NEW: rail/coach/ferry/cruise compensation recovery engine — UK Delay Repay, EU Rail 2021/782, f...
AI agents use transitpulse to commit financial operations through Pulsenetwork — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | Destination neighborhood or address |
city | string | — | City name (e.g. London, NYC, Tokyo; default: London) |
from | string | — | Origin neighborhood or address |
lang | string | — | Letter language (default English) |
line | string | — | Specific line or route to focus on |
mode | string | — | Transport mode |
time | string | — | Time of travel (e.g. 9am, rush hour) |
cause | string | — | Disruption cause (default unknown — exemption burden is the operator's) |
route | string | — | Line or route name (e.g. L train, Northern line) |
action | string | Yes | Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visito |
cities | string | — | Alternative: comma-separated pair (e.g. NYC,London) |
city_a | string | — | First city |
Parameters from the server's own tool schema.
Every invocation of this tool triggers a micropayment in USDC on the Base blockchain, committing real financial obligations per query. Additionally, the compensation recovery engine generates legal claim letters that could initiate financial recovery processes. The payment-per-query model makes this Financial under the most-severe-category rule, even though the underlying data retrieval is informational.
From the tool's definition agents pay per query via x402 USDC on Base; deterministic eligibility ($0.10) + citation-locked claim letters ($2.00); endpoints priced at $0.05, $0.08
Risk signalsHigh parameter count (37 properties)
Attacks that exploit this kind of access
TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide. NEW: rail/coach/ferry/cruise compensation recovery engine — UK Delay Repay, EU Rail 2021/782, ferry 1177/2010, coach 181/2011, US FMC cruise refunds, Athens Convention baggage — deterministic eligibility ($0.10) + citation-locked claim letters ($2.00). Coverage: Global Endpoints: • status ($0.05): Live Service Status • city ($0.08): City Transit Intelligence Brief • route ($0.08): Route Reliability Analysis • commute ($0.10): Commute Quality Analysis • airport ($0.08): Airport Transit Guide • agencies ($0.05): Transit Agencies Lookup • delays ($0.05): Current Transit Delays • delays-history ($0.08): Historical Delay Patterns • trip ($0.05): Transit Trip Planning • multimodal ($0.10): Multi-Modal Journey Planning • compare ($0.12): City-to-City Transit Comparison • carfree ($0.12): Car-Free Livability Score • visitor ($0.08): First-Timer Visitor Guide • coverage ($0.10): Transit Coverage Analysis • check ($0.10): Rail/Coach/Ferry/Cruise Compensation Eligibility Check • letter ($2.00): Citation-Locked Transit Compensation Claim Letter. 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.
transitpulse accepts 12 parameters: to, city, from, lang, line, mode, time, cause, route, action, cities, city_a. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for transitpulse: 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.
transitpulse is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transitpulse 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.
Set action: deny in the PolicyLayer policy for transitpulse. 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.
transitpulse 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.
transitpulse 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 →