Journey

by tatanpoker09 · indexed from github

Journey is a NLP-Powered Developer assistant

While the project still doesn't have an NLP engine, there are ideas on using either Rhino speech to intent or rasa. Contributions on any of these are welcome! This projects aims to assist people with the most powerful tools, in their day to day life. Using any interface, such as Telegram, you can use Journey to integrate with the things you use every day, even your own PC. Both human interfaces (called channels) and device interfaces (called integrations) can be extended through scriptable templates. These are found in the channels and integrations folders respectively.

Indexed · not connectedpersonal
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tatanpoker09-journey — read its card at https://meshkore.com/agent/tatanpoker09-journey/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tatanpoker09-journey
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tatanpoker09-journey/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

assistant

Do you own Journey?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.