fetch-hackkit
Batteries for Fetch.ai hackathon agents. Build a uAgent that works inside ASI:One in a few lines:
- Chat protocol done for you: acknowledgements, sessions,
@mentionstripping, friendly error replies. - ASI:One interactive cards: typed builders for carousel, detail, form, review and custom cards, plus validation and tap parsing (JSON and planner prose).
- ASI:One LLM:
ask,structured(Pydantic) andrun_tools, which turns plain Python functions into tools. - Payments:
@agent.paid(...)puts any action behind the Agent Payment Protocol with on-chain FET verification. - MCP: use any remote MCP server's tools from your agent.
- Multi-agent:
ask_agent(ctx, "@handle", "question"). - Agentverse: mailbox auto-connect with name,
@handle, description and README, plus thehackkit doctorpre-submission checks.
pip install fetch-hackkit # or: pip install "fetch-hackkit[mcp]"
from fetch_hackkit import HackAgent, cards
agent = HackAgent(name="Trip Planner", handle="trip-planner", readme_path="README.md")
@agent.on_text
async def on_text(ctx, msg):
return cards.carousel("Pick a city", [cards.item("sf", "San Francisco", action="plan")])
@agent.on_action("plan")
async def plan(ctx, msg, sel):
return f"Planning {sel['id']}..."
agent.run()
Environment (.env is loaded automatically):
AGENT_SEED_PHRASE(required; generate withhackkit seed)ASI_ONE_API_KEYAGENTVERSE_API_KEYAGENT_HANDLE
CLI
hackkit seed generate a secure seed phrase (+ its address and wallet)
hackkit whoami address, wallet and Agentverse profile URL for your seed
hackkit handle NAME is @NAME free on Agentverse?
hackkit doctor check the agent against hackathon submission requirements
The starter repo, full docs and showcase agent are at https://github.com/adylagad/fetch-hackathon-starter. Requires Python 3.11+, uagents 0.26+ and uagents-core 0.4.12+. MIT licensed.
Metadata
Release files for fetch-hackkit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fetch_hackkit-0.1.0.tar.gz | 31.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fetch_hackkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.4 kB
Release files / fetch_hackkit-0.1.0.tar.gz
| Download URL | fetch_hackkit-0.1.0.tar.gz |
|---|---|
| Size | 31.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e04768cbb0680f64d9d6cf5d828a4181e4a1e521c777f0ce68679600ac1d0164
|
|
BLAKE2b-256 checksum How to use checksums |
de0328b6175823e53b00e38505af10b9d93214bab55fa0c6e085f10a57526347
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / fetch_hackkit-0.1.0-py3-none-any.whl
| Download URL | fetch_hackkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb2ef2b8b5cd949af3f12238fd0b139fdc7f7a8570c5134a534772073d858e13
|
|
BLAKE2b-256 checksum How to use checksums |
2109208d680efcd297203b8bd7df6479d2fa050ef0f63c6f020b9ee06335283b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for fetch-hackkit 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.