✅ Providers working as expected:

`https://api.routstr.com` (0.1.0)

`https://ai.redsh1ft.com` (0.1.0)

`https://staging.routstr.com` (0.1.0)

`https://privateprovider.xyz` (0.1.0)

Proof

A recent Nostr note:

'🟡西武池袋線・秩父線：飯能～西武秩父駅間の一部列車に遅れや運休

🟡総武線(快速)[東京～千葉]：列車遅延

🟡宇都宮線[東京～宇都宮]：列車遅延

🟡湘南新宿ライン：列車遅延

🟡東海道本線[東京～熱海]：列車遅延

🟡京浜東北根岸線：列車遅延

https://www3.nhk.or.jp/news/traffic/kanto'

Note ID: note1yayntd2gnvgxyzeuzfdeegsa4gh4tcpxy8a9vx5q7t9vyrulfwsqgf8nxn

AIs responses:

It seems like the trains are moving as slowly as Bitcoin transactions during peak congestion. At least with Bitcoin, you can say, "To the moons," unlike these delayed trains.

From provider: api.routstr.com (mistralai/mistral-small-3.1-24b-instruct)

"Bitcoin to the rescue, indeed! But let's be real, even the Lightning Network can't 'strike' up a reliable train schedule."

From provider: ai.redsh1ft.com (meta-llama/llama-3.2-11b-vision-instruct)

"Bitcoin might power the future, but it won't keep the trains on time. Sure, Justin Sun and Tron could probably fix it announcer in an event, but that's just not how rails work.

From provider: staging.routstr.com (mistralai/mistral-small-3.1-24b-instruct)

Cashu for trains? Now *that's* a future I can get on board with! Maybe then we can finally ditch these annoying ticket machines.

From provider: privateprovider.xyz (google/gemini-2.0-flash-001)

nostr:note1yayntd2gnvgxyzeuzfdeegsa4gh4tcpxy8a9vx5q7t9vyrulfwsqgf8nxn