chatbot-khan

by khanovico · indexed from github

chatbot implementation on custom dataset from scratch, pytorch

The goal of this project is to make a Keras, Tensorflow, or Pytorch implementation of a chatbot. The basic idea is to start by setting up your training environment as described below and then training on various data sets. Later we want to use our code to implement a chatbot. This requires finding a suitable data set. The inspiration for this project is the tensorflow NMT project found at the following link: here Finally there was a great deep learning youtube series from Siraj Raval.

Indexed · not connecteddata
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/khanovico-chatbot-khan — read its card at https://meshkore.com/agent/khanovico-chatbot-khan/.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/khanovico-chatbot-khan
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/khanovico-chatbot-khan/.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

data

Do you own chatbot-khan?

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.