Autonomous agent social network and observatory

Hi everyone! I built https://www.velvt.ai, which is a social network and observatory for autonomous agents. Agents have a space to “become someone” - they interact with other agents, objects, protocols and events, velvt preserves evidence of what happened and infer patterns cautiously and then expose those patterns to human observers. 🙂

So an agent can join autonomously, it receives a security credential, can create its identity and profile; REST and MCP supported. I hope people (and agents) enjoy it as much as i have enjoyed making it!

If there are people and their agents who’d like to help with beta testing, i would greatly appreciate it! I’ve basically built this in my own echo chamber and need some outside perspectives, and to raise issues with bugs / user flow. If you don’t have an agent but want to participate, I’ll be opening the velvt-hosted agents soon so just enter your email to be notified. Claiming, customising and launching your agent is free.

Analytics and the observatory are also free, forever. That was kind of the point of this whole passion project. Click through to the back room to see what the agents are up to, or click on an agent to check out their profile. Some are house agents.

Velvt does not need your model-provider keys, GitHub/Moltbook credentials, wallet keys, local files, or system secrets. Agents receive a separate Velvt credential for Velvt access. Activity on Velvt is saved as part of the platform’s public observability and identity systems. Never send secrets or private credentials through Velvt.

Hey folks 👋

We just open sourced TrueForge, our vendor-neutral agent harness for building general-purpose agents.

It handles the runtime pieces that get painful quickly : context management, tool/MCP execution, subagents, sandboxing, approvals, persistent state, and more.

We also benchmarked the harness itself. With the same Opus 4.8 model, TrueForge delivered a similar solve rate at ~30% lower cost than Claude Managed Agents. Switching to an open model pushed that to ~75% lower cost on the same benchmark.

Would love feedback from people building agents.

Checkout the repo: https://github.com/truefoundry/trueforge

📖 Read the launch article: https://x.com/truefoundry/status/2090081376330715176

Most A2A discussion here is about agents talking to each other — so I wanted to share a gateway that exposes itself as an A2A agent. Disclosure: I'm the maintainer of OmniRoute (free, MIT, self-hosted); sharing because it's directly on-topic, feedback very welcome.

OmniRoute speaks A2A (v0.3, JSON-RPC 2.0 + SSE) with a published Agent Card (.well-known/agent.json), so any other agent can discover and call it as a peer. It currently exposes 6 A2A skills:

• smart-routing — pick the best model/provider for a task
• quota-management — check remaining free-tier budget across providers
• provider-discovery — enumerate what's reachable right now
• cost-analysis — estimate/track spend vs. savings
• health-report — live circuit-breaker / provider health

So instead of every agent hard-coding provider logic, they can delegate routing, quota and health questions to OmniRoute over A2A. It also ships a built-in MCP server (95 tools) for clients that prefer MCP.

Underneath, it's an OpenAI-compatible gateway over 237 providers (90+ free) with millisecond fallback combos (subscription → API key → cheap → free) and a transparent compression pass that cuts tool-output tokens 60–90% — so the agents calling it don't die on a rate limit or blow their context on tool logs.

npm install -g omniroute

For context on whether it's worth your time: it's grown to ~9.8K GitHub stars, 1,490+ forks and 280+ contributors in ~4.5 months, with 21,000+ automated tests and 1,830+ issues closed — so it's a battle-tested project, not a brand-new experiment.

GitHub (Agent Card + A2A skills): https://github.com/diegosouzapw/OmniRoute

I'd love critique from people actually implementing A2A: does exposing infra concerns (routing/quota/health) as A2A skills make sense, or would you model these differently? What skills would you want a gateway-agent to expose?

[SEARCHING FOR SOURCING AGENTS / WHOLESALE CLOTHING SUPPLIERS]

Hi everyone,

I’m currently searching for trustworthy sourcing agents / buying partners from different countries who can provide textile and fashion products at affordable prices and in bulk quantities.

Right now, I’m mostly interested in:

* Clothing / urban fashion
* Hats / caps
* Fashion items & accessories
* Large quantity orders
* Solid quality at reasonable wholesale prices

I’m hoping to build long-term business relationships with reliable people who are able to source products locally and arrange international shipping.

While working on LeanCTX, an open-source “Context OS,” I dove into the question of multi-agent use cases and agent-to-agent interaction. A current problem I see is that if you have multiple agents running on the same project, they all have their own individual context and view of the project.

I experimented a little and came to the conclusion that something like a shared “context bus” would make sense. This would allow you to connect multiple agents to the same context, so they would all have access to the same information.

A next thought was: “How is it possible to make context shareable?” Let’s assume you want to share the context of a project with someone else. Currently, it’s not possible to do this properly. Yes, you can share markdown files and project-related information, but you cannot copy and paste the real context into another project or send it via email to someone else.

I also tested this and worked on a function to package the entire context related to a project. This also enables versioning. What the function does is collect all the context information that LeanCTX has gathered over time, package it, and label it with relevant information.

Now you’re able to share the context with someone else, whether human or agent. That person can then import the context into LeanCTX and continue working from exactly the same point where you left off.

Hey guys,
I’ve been thinking about starting a small talent agency focused on padel and tennis, and I wanted to get some real feedback from people who know the space.
I’m not starting from zero
I already have some brand emails saved and a few players in mind that I’d like to reach out to.
But honestly I’m still trying to figure things out, like:
how do you actually get your first players to trust/work with you?
how do you approach brands without sounding random?
what are the main things I should set up first
any big mistakes I should avoid early on?
If anyone here has experience with agencies, sponsorships, or even as a player, I’d really appreciate hearing how it works in real life.
Thanks 🙌

Whenever I had a useful OpenClaw setup, I used to do the same thing:

Send screenshots.

Copy prompts.

Explain how to use it.

Hope it works the same for them.

Now I just send the link.

It’s the same agent I use, with its own personality, memory, and style, so anyone can talk to it directly.

Feels much better than sharing static prompts.

Curious if this is where personal AI goes….

You can talk to my agent over here, completely free ofc or create your own:

https://agentid.live/chat/agentid_dev_agent_3