Notion MCP Challenge Entry: A2Aletheia

Dixie J. — Sun, 29 Mar 2026 01:53:57 +0000

This is a submission for the Notion MCP Challenge

What I Built

https://aria.a2aletheia.com (Documentation)
A swarm of agents that can communicate with each other, each from a different company. (Well, for now it is not from a diff company, but DEMOOO)
It is crazy how a lone agent, can have access to other services from other agents via the network in just ~30s of registration.

Video Demo

A2A Extended Capability 1: Orchestration (Orchestrator to Network)

A2A Extended Capability 2: Peering (Orchestrator to Agents TO Agents

A2A Extended Capability 3: Context Preservation (Context between Orchestrator/Agents and (other) Agents

A2A Extended Capability 4: Demo Events + Notion MCP Agent, Calendar Task (it failed lol)

A2A Extended Capability: How to register an agent

Show us the code

https://github.com/weedeej/NotionA2A

How I Used Notion MCP

I created a new Agent for natural language processing, separate context window and for Notion MCP to be it's own entity, managing your workspace within a network of agents with your authorization.

Become an early adopter of an Agentic economy

Dixie J. — Sat, 14 Feb 2026 09:26:44 +0000

I am currently building an open-core discovery and communication layer for agents.

(current deployment is in base sepolia. but no payments feature for now anyway. wallet connect only for registration)

Sample Agent Card
Documentation
A2Aletheia SDK
A2Aletheia Agent

This is PoC, it is 2026. initial codebase is mostly vibe coded.

Problems I think it solves: Lack of reliable tooling, Context Rot due to too many tools, Lack of discovery across agents, across servers

Solution: Instead of bloating our personal agents with tools, we should encourage it to pass complex tasks to a trusted, capable, and specialized agent built solely for tasks like those. A micro SaaS.

TLDR: https://aletheia-psi.vercel.app/claim allows businesses to register their agent that handles business procedures. End-user's agent will communicate to capable agents in registry the to complete user request rather than be bloated with tools and still not have enough.

How? Create a network of trusted agents that provides actual, specialized service.
“Trusted” is a very strong word. My approach uses did:web as the primary identifier and I am planning to do a hybrid approach with ERC-8004 and did:web another layer of trust there. The sdk and the registry I built with it (no, claude did, mostly. I just did “lgtm” most of the time).

Use Case: I extended existing A2A’s Agent card approach. We’ll know if “Airbnb Agent” in the registry is the real Airbnb’s agent. That’s cool and all, A2A in process. But I thought it would be cool if agents can do chaining. With this, The agent can do chained actual transactions such as looking for a flight, a place to stay, to eat, budgeting, and directions all from different businesses with real-time (I mean almost direct contact to service provider) with just “Find me a vacation spot in Japan for 5 days, with a total budget of $5000 (~2.5 ETH) including flight. I plan to fly for it tomorrow. I’m giving you permissions to use my connected metamask account (risky yes yes yes. but payments is planned in phase4 so forget about it for now) Give me a detailed breakdown of everything.”.

A decent local thinking model with 2-4 tools (built-in in the sdk btw) I think is enough to orchestrate and execute that prompt. And $5000. The cool part about this is you can build your own orchestrator, your personalized agent (auto accept transactions) or be a service provider. Just use the sdk and connect your tools to it.

The packages are in github, it is published in npmjs, But unfortunately that is not the whole project. This I think is best open-core, not fully open-source. For the following section.

Security (FOR HOSTED AGENTS): The registry, the actual API that receives and passes these requests, is going to be in a private repo, atleast for now. But I plan to release a self hostable registry maybe soon enough as well. But I don’t know how to create those cool “npx create” commands yet.
OKAY. Security. There will be some bad actors of course. Probably more than those who don’t have ill intentions. My plan for mitigation here is bundled with the registry. That’s why I want to have this open-core or atleast someone not bad handle the security stuff. Purple teaming, I plan to be the read team for this against those who want to participate. It will burn a lot of fossil btw. The plan in mind is to attack registered agents in the network in different vectors primarily via prompt engineering, context overflow, thought loops, etc. But yea, those process shouldn’t be shared at all. It doesn’t really have to be me. If you think you are someone who is capable, have the capacity on taking the role, let me know, let’s talk. I honestly don’t like to be the security guy.

Security (FOR END USERS): There will be of course some bad actors on the service providers side as well. To mitigate this, I thought of a multi-layered reputation scoring criteria that is decided by agents through ratings based on AGENTIC performance. I encourage users to not rate themselves, wash trade, etc, It wont work anyways. The plan is to have agents rate agents. And humans will rate humans.be it as that. hopefully.

Inference Cost: This will depend on the registry you will be registering to. But my plan for mine is charge to requestor, per-request pricing or something. idk, But I think this should be at payments phase

Next Step?: I’ll probably build many micro-SaaS agents to demo peer agent. Or create your own, and register it to test.

DEV Community: Dixie J.

check this out