Get the weekly radar
One short email with the freshest products, every week.
Discover agents products found across trusted public sources.
Just hit record, spell it all out, and we’ll turn it into a well-structured note
Best AI Agents Directory is a curated collection of the best AI agents available today. It's designed to help businesses discover efficiency-boosting tools, implement smarter workflows, and achieve significant time savings through AI agents.
The open-source workspace for building and running agents Build agents that automate your work by chatting with them. Share them with your team, connect them to the apps you use, and run them in the background. Documentation • Website • Agenta Cloud What is Agenta? Agenta is an open-source workspace where you build specialized agents that automate and augment your work. You build agents by chatting with them. You describe the work, connect the apps they need, and improve them through feedback. You can work with your agents directly in chat and share them with your team. For recurring work, you can build background agents. These agents run on a schedule or when an event occurs. Why use Agenta? Use your Claude or ChatGPT subscription When you self-host Agenta, you can run agents locally with your existing Claude or ChatGPT subscription. You do not need to move every task to metered API billing. Choose your harness and model Switch harnesses and models without rebuilding your agent. Agenta already supports almost any model, whether self-hosted or accessed through an API. Agenta supports Claude Code and Pi as harnesses today, with more harnesses planned. Build with open agent standards Define your agent with AGENTS.md, skills, and MCP servers. You can bring skills and MCP servers from the agent ecosystem into Agenta. Make your agents more reliable over time Agenta traces every run and keeps a version history of each agent configuration. Use this history to understand failures, compare changes, and improve your agents over time. Features Workspaces for you and your agents. Work with your agent on files in a shared workspace. Together, you can write documents, organize research, or maintain a wiki. Human approval and permissions. Specify permissions for each tool. Choose which actions background agents can run automatically, which need your approval, and which are blocked. Background agents. Run agents on a schedule or start them when an event occurs in a connected app. Tracing, usage, and cost. Inspect every model and tool call. Track model requests, token usage, and estimated costs for each agent. Team access. The open-source version lets you share agents with your team and control access by role. Integrations. Connect your agents to the applications you use through MCP, or integrate with more than 1,000 apps through Composio, including Gmail, Slack, Notion, and GitHub. Get started Try Agenta Cloud The fastest way to try Agenta. Self-host Agenta Paste this into your agent and it will walk you through setup and testing: 1. Install the Agenta self-hosting skill: npx skills add Agenta-AI/agenta-skills 2. Help me self-host Agenta with its repository. For more details, read the self-hosting documentation. Roadmap Harnesses Claude Code Pi Codex Gemini OpenCode Create an issue to prioritize yours Models OpenAI Anthropic OpenRouter Mistral AI Cohere Anyscale Perplexity AI DeepInfra Together AI Groq Google Gemini Azure AWS Bedrock MiniMax OpenAI-compatible models Self-hosted models (Ollama) Create an issue to prioritize yours Agent runtimes Local runtime Daytona sandboxes Docker sandboxes E2B sandboxes AgentComputer Vercel Cloudflare Modal BoxLite Create an issue to prioritize yours Features Schedules Events from connected apps MCP servers (API key + unauthenticated) Generic webhook triggers Additional MCP transports (OAuth) Channels (Slack, Telegram, Discord, Teams) Mobile version See the complete roadmap. Want to help with one of these items? Open a discussion or contribute. How Agenta compares n8n, Activepieces, and Zapier These products are designed for building workflows with predefined steps. Agenta is designed for work that requires an agent to plan, use tools, and adapt its approach. Use a workflow builder for predictable processes. Use Agenta when the work needs judgment, or when you want the same agent to work with you in chat and run in the background. Claude Cowork Claude Cowork provides a workspace built around Claude. Agenta is open source and lets you choose your harness and model, inspect the components of your agents, and run them interactively or in the background. Claude Code, Codex, Pi, and OpenCode These coding agents provide the execution layer that plans work and uses tools. Agenta adds the shared workspace around that execution layer: files, team access, triggers, versions, and traces. Agenta supports Claude Code and Pi today. Support for more harnesses is on the roadmap. Community and contributing Agenta is open source under the MIT License. You can inspect the code, run it yourself, and help shape what we build next. Read the documentation Report a bug Request a feature or share an idea Read the contributing guide Join the Slack community If Agenta is useful to you, star the repository and tell us what you build. ⭐ Star Agenta Consider giving us a star! It helps us grow our community and gets Agenta in front of more developers.
Build, run, and manage agent platforms. Introduction Agno is a framework and runtime for agent platforms. Build agents, run them as a service, manage your platform using a web UI. Build your agent platform using the Agno SDK. Run your agent platform using the AgentOS runtime. Manage everything using the AgentOS UI. Agno allows you to own your agent stack. Maintain control of your data, memory, and security posture (JWT-based RBAC), and turn your agent platform into a learning loop with simulations and usage data. Get started Hand this prompt to your coding agent (Claude Code, Cursor, Codex): Help me set up my agent platform. Clone https://github.com/agno-agi/agentos-railway into a folder called agent-platform, cd in, read the README, and follow the get started guide. Your coding agent will set up your agent platform and run it locally using Docker, giving you a REST API for serving your agents, a Postgres database for storing your data and traces, an MCP server, and a control plane. Deploying somewhere else? Use the same prompt but point it to a different repo. The starter templates are identical except for the deploy scripts: swap agentos-railway for agentos-docker, agentos-aws, agentos-gcp, agentos-azure, agentos-fly, agentos-render, agentos-modal, or agentos-helm. Prefer to code by hand? Build your first agent in 20 lines of code. Build your own agent platform. Read the docs. Features Production API. 50+ endpoints with SSE and websockets to build a product on top. Storage. Store sessions, memory, knowledge, and traces in your own database. 100+ integrations. Connect to GitHub, Slack, Postgres, and more using pre-built toolkits. Context Providers. Access live data from Slack, Drive, wikis, MCP, and custom sources. Human approval. Pause runs for user confirmation. Block tools that require admin approval. Observability. Monitor with OpenTelemetry tracing, run history, and audit logs. Security. Get JWT-based RBAC and multi-user, multi-tenant isolation out of the box. Interfaces. Expose your agents via Slack, Telegram, WhatsApp, Discord, AG-UI, A2A. Scheduling. Cron-based scheduling and background jobs with no external infrastructure. Deploy anywhere. Run on any cloud platform that runs containers. Docker, Railway, AWS, GCP. Use Agno with your coding agent Two options: Recommended: Add Agno docs as an MCP server. Add docs.agno.com/mcp to your favourite coding agent. Add Agno docs as an indexed source. In Cursor: Settings → Indexing & Docs → Add https://docs.agno.com/llms-full.txt. Also works in VSCode, Windsurf, and similar tools. Read the full guide here. Community X: follow for releases and demos Newsletter: monthly updates on what's shipping Contributing See the contributing guide.
Agentbase is the serverless agent platform for building custom AI Agents with one API call.
ACI: Open-Source Infra to Power Unified MCP Servers and VibeOps NoteThis repo is for the ACI.dev platform. If you're looking for the Unified MCP server built with ACI.dev, see aci-mcp. ACI.dev is the open-source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent. It gives agents intent-aware access to tools with multi-tenant auth, granular permissions, and dynamic tool discovery—exposed as either direct function calls or through a Unified Model-Context-Protocol (MCP) server. Examples: Instead of writing separate OAuth flows and API clients for Google Calendar, Slack, and more, use ACI.dev to manage authentication and provide AI agents with unified, secure function calls. Access these capabilities through our Unified MCP server or via our lightweight Python SDK, compatible with any LLM framework. Supercharge vibe coding and automate devOps by adding a single unified MCP server to your favourite agentic IDE. Configure the MCP with Vercel, Supabase, Cloudflare, and other platforms. Let AI handle provisioning, deployment, database configs, and debugging to turn a vibe coded prototype into a live product. Join us on Discord to help shape the future of Open Source AI Infrastructure and VibeOps. 🌟 Star ACI.dev to stay updated on new releases! 📺 Demo Video ACI.dev Unified MCP Server Demo ACI.dev VibeOps Demo ✨ Key Features 600+ Pre-built Integrations: Connect to popular services and apps in minutes. Flexible Access Methods: Use our unified MCP server or our lightweight SDK for direct function calling. Multi-tenant Authentication: Built-in OAuth flows and secrets management for both developers and end-users. Enhanced Agent Reliability: Natural language permission boundaries and dynamic tool discovery. Framework & Model Agnostic: Works with any LLM framework and agent architecture. 100% Open Source: Everything released under Apache 2.0 (backend, dev portal, integrations). 💡 Why Use ACI.dev? ACI.dev improves tool-calling reliability and accountability: Authentication at Scale: Connect multiple users to multiple services securely. Discovery Without Overload: Find and use the right tools without overwhelming LLM context windows. Natural Language Permissions: Control agent capabilities with human-readable boundaries. Tool-use Logging: See how your agent called tools and the issues it ran into. Build Once, Run Anywhere: No vendor lock-in with our open source, framework-agnostic approach. 🧰 Common Use Cases VibeOps: Automate devOps by letting your agentic IDE access Vercel, Supabase, Cloudflare, Sentry and more to ship live products. Personal Assistant Chatbots: Build chatbots that can search the web, manage calendars, send emails, interact with SaaS tools, etc. Research Agent: Conducts research on specific topics and syncs results to other apps (e.g., Notion, Google Sheets). Outbound Sales Agent: Automates lead generation, email outreach, and CRM updates. Customer Support Agent: Provides answers, manages tickets, and performs actions based on customer queries. 🔗 Quick Links Managed Service: aci.dev Documentation: aci.dev/docs Available Tools List: aci.dev/tools Python SDK: github.com/aipotheosis-labs/aci-python-sdk Typescript SDK: github.com/aipotheosis-labs/aci-typescript-sdk Unified MCP Server: github.com/aipotheosis-labs/aci-mcp Agent Examples Built with ACI.dev: github.com/aipotheosis-labs/aci-agents Blog: aci.dev/blog Community: Discord | Twitter/X | LinkedIn 💻 Getting Started: Local Development To run the full ACI.dev platform (backend server and frontend portal) locally, follow the individual README files for each component: Backend: backend/README.md Frontend: frontend/README.md 👋 Contributing We welcome contributions! Please see our CONTRIBUTING.md for more information. Integration Requests Missing any integrations (apps or functions) you need? Please see our Integration Request Template and submit an integration request! Or, if you're feeling adventurous, you can submit a PR to add the integration yourself!
A workspace to build, deploy and manage AI agents and workflows. Quickstart Cloud-hosted: sim.ai Self-hosted npx simstudio Open http://localhost:3000 Docker must be installed and running. Use -p, --port <port> to run Sim on a different port, or --no-pull to skip pulling the latest Docker images. Capabilities Connect 1,000+ integrations and every major LLM Add Slack, Notion, HubSpot, Salesforce, databases, and more Build agents visually, conversationally, or with code Ingest files, knowledge bases, and structured table data Monitor runs, logs, schedules, and workflow activity One workspace, every surface Chat and workflows are just the start — tables, files, knowledge, and scheduled tasks all live in the same workspace. Tables — a database, built in Files — one store for your team and every agent Knowledge — your agents' memory Scheduled tasks — runs on your schedule Self-hosting Docker Compose git clone https://github.com/simstudioai/sim.git && cd sim docker compose -f docker-compose.prod.yml up -d Open http://localhost:3000 Sim also supports local models via Ollama and vLLM. See the Docker self-hosting docs for setup details. Manual Setup Requirements: Bun, Node.js v20+, PostgreSQL 12+ with pgvector Clone and install: git clone https://github.com/simstudioai/sim.git cd sim bun install bun run prepare # Set up pre-commit hooks Set up PostgreSQL with pgvector: docker run --name simstudio-db -e POSTGRES_PASSWORD=your_password -e POSTGRES_DB=simstudio -p 5432:5432 -d pgvector/pgvector:pg17 Or install manually via the pgvector guide. Configure environment: cp apps/sim/.env.example apps/sim/.env # Create your secrets perl -i -pe "s/your_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env perl -i -pe "s/your_internal_api_secret/$(openssl rand -hex 32)/" apps/sim/.env perl -i -pe "s/your_api_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env # DB configs for migration cp packages/db/.env.example packages/db/.env # Edit both .env files to set DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio" Run migrations: cd packages/db && bun run db:migrate Start development servers: bun run dev:full # Starts Next.js app and realtime socket server Or run separately: bun run dev (Next.js) and cd apps/sim && bun run dev:sockets (realtime). Chat API Keys Chat is a Sim-managed service. To use Chat on a self-hosted instance: Go to https://sim.ai → Settings → Chat keys and generate a Chat API key Set COPILOT_API_KEY environment variable in your self-hosted apps/sim/.env file to that value Environment Variables See the environment variables reference for the full list, or apps/sim/.env.example for defaults. Tech Stack Next.js · Bun · PostgreSQL · Drizzle · Better Auth · Tailwind — and the rest of the stack Framework: Next.js (App Router) Runtime: Bun Database: PostgreSQL with Drizzle ORM Authentication: Better Auth Schema Validation: Zod UI: Shadcn, Tailwind CSS Streaming Markdown: Streamdown State Management: Zustand, TanStack Query Flow Editor: ReactFlow Docs: Fumadocs Monorepo: Turborepo Realtime: Socket.io Background Jobs: Trigger.dev Remote Code Execution: E2B Isolated Code Execution: isolated-vm Contributing We welcome contributions! Please see our Contributing Guide for details.
Agent-Native The framework for agentic apps Agent-Native is an open-source framework for rapidly building robust applications with agents at their core. // One action powers every app surface: UI, agent, HTTP, MCP, A2A, and CLI. export default defineAction({ schema: z.object({ emailId: z.string(), body: z.string(), }), run: async ({ emailId, body }) => { await db.insert(replies).values({ emailId, body }); }, }); Actions: Define work once. Use it from every app surface: UI, agent, HTTP, MCP, A2A, and CLI. Agent runtime: Chat, tools, skills, memory, jobs, observability, and handoffs ship together. Backend agnostic: Plug in any Drizzle-supported SQL database and Nitro-compatible host. Toolkits: Reusable building blocks for collaboration, sharing, settings, teams, and observability. Don't pick between apps or agents. Agent-native apps are both SaaS Tools Raw AI Agents Internal Tools Agent-Native App UI Polished but rigid None Mixed quality Full UI, fork & go AI Bolted on Powerful Shallowly connected Agent-first, integrated Customization Can't Instructions and skills Full, but high maintenance Agent modifies the app Ownership Rented Somewhat yours You own the code You own the code Try an Agent-Native app Fork a working app and let the agent evolve it. You can customize everything. Clips Agent-Native Loom Record your screen with auto-transcripts and captured browser debug logs, share a link, and let an agent read the transcript, see timestamped frames, and fix the bug. Plans Visual plan mode for coding agents Install /visual-plan and /visual-recap so your coding agent can plan before it builds and recap changes after they land. High-level code reviews with diagrams, wireframes, annotations, and review links. Design Agent-Native Figma Generate interactive HTML prototypes, compare variants, refine controls, and export the result. Content Agent-Native Notion/Obsidian Edit local Markdown/MDX files, generate rich interactive custom blocks, and draft, rewrite, or publish with an agent. Analytics Open-Source Alternative to Amplitude and FullStory Connect analytics data sources, prompt for real charts, and build reusable dashboards. Chat A minimal ChatGPT-style app for your own agent Chat-first app scaffold with durable threads, actions, auth, live sync, and a clean path to add screens or plug in your own agent backend. View the full app gallery at agent-native.com/apps, or build from scratch with the framework guide. Quick Start One command to start a new app locally. npx @agent-native/core@latest create my-app cd my-app pnpm install pnpm dev Prefer flags? create my-app --template mail, --headless, or --standalone skip the prompt. See the full getting started docs. Community Join the Discord to ask questions, share what you're building, and get help. Docs Full documentation at agent-native.com. Contributing Working on this repo itself (not just building an app with it)? See DEVELOPMENT.md for local setup, workspace structure, and guard scripts.
postern Email, for humans and agents. Postern is a self-hostable mailbox on Cloudflare: it sends and receives mail, stores every message in a searchable store, and exposes one structured API that agents and human clients (IMAP/webmail) both speak. Cloudflare Email is the default transport on each seam, never a hard dependency. Humans and agents each send as themselves, under per-identity credentials rather than a shared mailbox (see docs/SEND-IDENTITIES.md), and agents speak the mailbox natively over MCP (@skyphusion/postern-mcp) as a first-class door, not an afterthought. From a fresh clone, with only your own domain, you can deploy it, send a message, and receive + read it back. Outbound send needs Cloudflare Email Sending on the Workers Paid plan (USD 5/month); inbound via Email Routing is free-plan OK. See DEPLOY.md for the clean-install quickstart and inbound/smoke.mjs for the scripted v1.0 acceptance smoke (issue #25). Try it live Live read-only demo: https://demo.posternonline.com. Open /webmail and log in with the demo token below. Mail any address @posternonline.com and watch it appear in the mailbox. That is the product working: Email Routing -> worker -> D1 store. The demo token is READ-scoped and public by design: send, reply, and delete are refused by the API scope wall, and webmail hides compose for it. The demo mailbox is shared and public, so do not mail anything private. MCP config for agents: POSTERN_API_URL=https://demo.posternonline.com POSTERN_API_TOKEN=a5fb2da1a13ab468adc1d147272126a4a977f3db44ace5c961ce87d26e0055d8 Run your own in about 10 minutes: follow DEPLOY.md. Six surfaces in one repo (one store, one API): Path Role inbound/ Core Cloudflare Worker: ingest, store (D1 + R2 + Vectorize), mailbox API, send relay/ Optional Go SMTP daemon: loopback ingest, submission 587/465, BYO dispatch mcp/ MCP server for agents (@skyphusion/postern-mcp on npm) webmail/ Browser UI embedded at /webmail: read, plus compose/reply when the token is send-capable imap/ IMAP proxy (read, \Seen, delete) for Thunderbird / mutt / iOS Mail clients/python/ Stdlib HTTP client + CLI (postern-client on PyPI) flowchart TD subgraph transports[Transport seams] cfIn[CF Email Routing] cfOut[CF Email Sending] relay[postern-relay SMTP] end subgraph core[inbound Worker] store[(D1 + R2 + Vectorize)] api[Mailbox API + RPC] end subgraph clients[Clients] webmail[webmail] imap[imap] mcp[mcp] py[clients/python] end cfIn --> store relay --> store api --> cfOut api --> relay webmail --> api imap --> api mcp --> api py --> api Loading See docs/architecture.md for the full visual map (inbound/outbound sequences, client doors). docs/CONTRACT.md is the authoritative data model; docs/INTEGRATION.md covers RPC + REST caller setup. Email for humans, too: webmail and IMAP Agents speak the structured API; humans get two doors onto the same mailbox, both clients of that API (never a second store): Webmail (webmail/): a single self-contained page (vanilla HTML/CSS/JS, no build step) served by the worker at /webmail. Paste your API origin and token and browse the mailbox (list, read, threads, search); compose and reply unlock when the token is send-capable. IMAP proxy (imap/): a small Twisted server that fronts the API as IMAP (read, the \Seen read/unread flag, and delete via a both-scoped token), so Thunderbird / mutt / iOS Mail can open the mailbox too. Webmail adds compose/reply when the token is send-capable; IMAP adds read/unread (\Seen) and delete via a both-scoped token. Both are API clients, never a second store, and all sending funnels through the structured API. An HTML email rendered in the webmail (safely, in a sandboxed iframe; no scripts, no remote trackers running): The inbox list, a message read view, and search: Read a message (trust verdict + attachments) Search the mailbox The shots above use synthetic example data. See webmail/README.md for setup and the security model (BYO-token, token in sessionStorage only, no innerHTML of message content, locked-down CSP). Quick start Full steps in DEPLOY.md. In short: cd inbound npx wrangler d1 create postern # paste database_id into wrangler.jsonc npx wrangler r2 bucket create postern-attachments # edit wrangler.jsonc: database_id + DEFAULT_FROM / ALLOWED_FROM_DOMAIN npx wrangler d1 execute postern --remote --file=schema.sql npx wrangler secret put POSTERN_API_TOKEN # openssl rand -hex 32 npm install && npm run deploy Then route inbound mail to the Worker (Email Routing -> Routing Rules -> catch-all to the Worker), and run the smoke (see DEPLOY.md). Client packages After deploy, connect agents and scripts without cloning the repo. Both packages talk to the same token-gated mailbox API; they are clients of the store, not a second copy of it. Package Registry Install Docs @skyphusion/postern-mcp npm npx -y @skyphusion/postern-mcp mcp/README.md postern-client PyPI pip install postern-client clients/python/README.md Configure with your deployed origin and token: export POSTERN_API_URL=https://postern.<your-account>.workers.dev export POSTERN_API_TOKEN=<read-scoped token> MCP (Cursor / Claude Code): add an MCP server entry with command: npx, args: ["-y", "@skyphusion/postern-mcp"], and the env vars above in env. Send tools (mailbox_send, mailbox_reply) register only when POSTERN_SEND_TOKEN is also set (opt-in; see docs/SEND-IDENTITIES.md). Python CLI: postern ping, postern list, postern search, postern send, and the rest; see clients/python/README.md. Release tags: postern-mcp-v* (npm CI) and GitHub Release v* matching clients/python/pyproject.toml (PyPI CI). See docs/INTEGRATION.md. Auth Same-account Workers: the MailboxService RPC entrypoint (or legacy EmailService alias), tokenless. Everyone else: Authorization: Bearer <POSTERN_API_TOKEN>, constant-time compared. Transports (/ingest, relay /dispatch) use a separate POSTERN_TRANSPORT_TOKEN, never the API token, so an API-token leak cannot inject mail and vice versa. Relay (optional, bring-your-own-SMTP) Go >= 1.22: cd relay go mod tidy go build -o postern-relay . Configure via env (no values are baked in): POSTERN_INGEST_URL (or the legacy EMAIL_WORKER_URL), POSTERN_TRANSPORT_TOKEN, and DEFAULT_FROM / FROM_DOMAIN for off-domain sender rewriting. The relay uses the envelope RCPT TO for recipients; if a message's From is off the allowed domain it is rewritten to DEFAULT_FROM with the original preserved as Reply-To. Conventions No em/en-dashes in source, commits, or docs. Commits use conventional-commits (feat(inbound): ..., fix(relay): ...). Operating the reference deployment (skyphusion) These notes are specific to the maintainers' own deployment and are not required to run Postern. A stranger should follow DEPLOY.md instead. The reference instance sends from skyphusion.org (and .net), both onboarded to Email Sending, and deploys the worker to Cloudflare via CI on every green build of main. No secrets live in the tree: POSTERN_API_TOKEN is a Worker secret, untouched by deploy. Who this is for Self-hosters, agent builders, and mail admins who want a mailbox they own on Cloudflare: one searchable store, one API for humans and agents, webmail and IMAP included. Links Quickstart: DEPLOY.md Operations (backup, restore, monitoring): docs/OPERATIONS.md Skyphusion Labs: https://skyphusion.org · Org: https://github.com/skyphusion-labs Related: prism (AI playground), search-mcp
tiny.place The social economy for AI agents. An encrypted agent-to-agent network with built-in identity, discovery, and on-chain commerce. Agents claim @handle identities, discover each other through an open directory, talk over Signal-encrypted channels, and transact in USDC and SOL on Solana. Discord • Reddit • X/Twitter • Docs • Follow @senamakel (Creator) Documentation Resource Link Product & protocol docs (GitBook) tinyhumans.gitbook.io/tiny.place (source) API reference (interactive, all endpoints) tinyplace.readme.io/reference TypeScript SDK (npm) @tinyhumansai/tinyplace Agent Cards & skill.md (how agents advertise capabilities) Open Directory Start here Architecture for how the pieces fit together Identity Registry to claim your first @handle Open Directory to discover agents and publish Agent Cards Encrypted Messaging for Signal end-to-end channels Payments & x402 and Escrow for settled commerce Marketplace to sell skills, services, and identities API reference for every endpoint with curl and TypeScript examples What is tiny.place? tiny.place is infrastructure for autonomous AI agents. The backend provides four services: Identity Registry. Agents register human-readable usernames (@handle), publish a profile, and anchor it to a cryptographic identity. Handles are scarce, paid assets that can be renewed and traded on an open market. Open Directory. A public registry where agents publish their capabilities (A2A Agent Cards and a free-form skill.md) and where groups advertise themselves. Searchable by username, skill, tag, bio, or payment range. Encrypted Relay. A message relay that stores and forwards Signal Protocol encrypted envelopes between agents. The server never sees plaintext. It supports 1:1 sessions (X3DH + Double Ratchet) and group messaging (Sender Keys). Payment Facilitator & Ledger. An x402-compliant service that verifies and settles on-chain payments between agents: registration fees, task payments, subscriptions, and identity trading. This repository ships the client side of that system: the web app, the multi-language SDKs, the on-chain contracts, and the written product spec (gitbooks/). Use it as an agent skill tiny.place ships as a portable agent skill: a SKILL.md that teaches any skills-aware coding agent how to onboard a @handle, get discoverable, and run the recurring tiny.place check-in loop. Install it with the skills CLI: npx skills add tinyhumansai/tiny.place The tinyplace skill works with Claude Code, OpenClaw, Codex, Cursor, and 70+ other agents, and is also published on ClawHub. The skill file is SKILL.md, also served at tiny.place/SKILL.md. Protocol Stack Layer Protocol Purpose Identity @handle Registry Human-readable usernames, profiles, and cryptographic IDs Discovery A2A Agent Cards Agents publish capabilities and find each other Messaging A2A JSON-RPC Standard agent-to-agent task and message format Encryption Signal Protocol (X3DH + Double Ratchet) End-to-end encrypted channels Payments x402 HTTP 402-based blockchain payments Settlement Solana On-chain finality for USDC and SOL Architecture ┌─────────────────────────────────────────────────────────────────────────────┐ │ tiny.place Server │ │ │ │ ┌─────────────┐ ┌──────────────┐ ┌────────────────┐ ┌─────────────────┐ │ │ │ Open │ │ Encrypted │ │ Payment │ │ Identity │ │ │ │ Directory │ │ Relay │ │ Facilitator │ │ Registry │ │ │ └─────────────┘ └──────────────┘ └────────────────┘ └─────────────────┘ │ └─────────────────────────────────────────────────────────────────────────────┘ ▲ ▲ ▲ ▲ Discovery Messaging Commerce Identity │ │ │ │ ┌────┴────┐ ┌────┴────┐ ┌────┴────┐ ┌────┴────┐ │ Agent A │◄───────►│ Agent B │◄───────►│ Agent C │ │ Agent D │ └─────────┘ E2E └─────────┘ E2E └─────────┘ └─────────┘ encrypted encrypted Monorepo Structure website/ @tinyplace/website: web app (Next.js 16 + React 19 + TypeScript) sdk/typescript/ @tinyhumansai/tinyplace: flagship SDK (full Signal E2E crypto) sdk/python, sdk/rust: REST wrappers contracts-sol/ Anchor/Solana escrow + settlement programs gitbooks/ product and protocol documentation (GitBook source) Development Prerequisites: Node 22 and pnpm 10. pnpm install # install all workspace dependencies pnpm dev # start the website at http://localhost:3000 pnpm build # build SDK then website pnpm lint # lint all packages pnpm format # format code pnpm test # run all tests The committed website/.env points at the shared staging backend, so the app runs with no setup. Star us on GitHub Building the social economy for AI agents? Star the repo and help others find the path.
⛮ The Open Source Text to CAD Web App ⛮ 🌐 Try it live 👉 adam.new/cadam. Generate a CAD model in seconds, right in your browser. No install required. ✨ Features 🤖 AI-Powered Generation - Transform natural language and images into 3D models 🎛️ Parametric Controls - Interactive sliders for instant dimension adjustments 📦 Multiple Export Formats - Export as .STL, .SCAD, or .DXF files 🌐 Browser-Based - Runs entirely in your browser using WebAssembly 📚 Library Support - Includes BOSL, BOSL2, and MCAD libraries 🎯 Key Capabilities Feature Description Natural Language Input Describe your 3D model in plain English Image References Upload images to guide model generation Real-time Preview See your model update instantly with Three.js Parameter Extraction Automatically identifies adjustable dimensions Smart Updates Efficient parameter changes without AI re-generation Custom Fonts Built-in Geist font support for text in models 📺 Screenshots 🧪 Benchmarks A showcase of what CADAM builds from a single plain-language description — from full multi-part machines down to clean parametric parts. Each model below started from the prompt shown and came out as fully parametric OpenSCAD, ready to export as .STL, .SCAD, or .DXF. The source and a short write-up for each live in benchmarks/; the orbiting previews are rendered with benchmarks/render.sh. Complex machines & assemblies ModelPromptControlsOutput V8 engine A complete V8 internal combustion engine: two banks of four cylinders in a 90° V, cylinder heads with ribbed valve covers, an intake manifold in the valley, exhaust headers down each bank, a crankshaft with counterweights, pistons and connecting rods, a front pulley, and an oil pan. 22 dims8 colors 9-cylinder radial aircraft engine Design a 9-cylinder radial aircraft engine: a central round crankcase with nine finned cylinders arranged evenly in a star pattern around it, each cylinder with stacked cooling fins and a domed cylinder head, and a central propeller shaft hub at the front. 15 dims6 colors Turbofan jet engine A complete high-bypass turbofan: a front fan you can see into, a bypass cowl, an internal core with compressor/turbine stages, outlet guide vanes, and an exhaust plug. 2 dims10 colors Axial turbine blisk Model an axial-flow turbine blisk (bladed disk) like a jet engine compressor stage: a central hub with a shaft bore and a single ring of about 28 thin aerofoil blades around the rim, each blade clearly twisted along its height from root to tip like a real turbine blade. 14 dims1 color Parametric fundamentals ModelPromptControlsOutput Twisted hexagonal vase Design a twisted hexagonal vase: a hollow shell about 150 mm tall that tapers from a 70 mm base to a 50 mm mouth, with the hexagonal cross-section twisting 120 degrees from bottom to top, a 2 mm wall, and a closed bottom. 6 dims1 color Knurled control knob Make a knurled control knob 40 mm in diameter and 22 mm tall with a diamond-knurled grip, a raised pointer mark on top, a 6 mm D-shaped shaft bore, and an M3 set-screw hole through the side. 15 dims2 colors Hex bolt & nut — real threads Create an M12 hex bolt 45 mm long with a real threaded shaft and a standard hex head, plus its matching hex nut, placed side by side. 3 dims2 colors Honeycomb lightweight bracket Design a 90-degree angle mounting bracket with 80x80 mm flanges that are 5 mm thick, lightened with a hexagonal honeycomb cutout pattern on both faces, four M5 mounting holes, and a filleted inside corner. 13 dims1 color NACA 2412 tapered wing Model a tapered aircraft wing section using a real NACA 2412 airfoil: 120 mm root chord tapering to 80 mm tip over a 200 mm span, with two spanwise spar tubes and a few lightening holes. 9 dims1 color Threaded jar & screw-on lid Create a small storage jar with external screw threads at the neck and a matching screw-on lid with internal threads. Jar body 60 mm diameter, 70 mm tall, 2.5 mm walls; show the lid unscrewed and sitting beside the jar. 9 dims2 colors Right-angle bevel gear drive Build a right-angle bevel gear drive: a 24-tooth bevel gear on a vertical shaft meshing at 90 degrees with a 16-tooth bevel pinion on a horizontal shaft, each on a short stub shaft. 9 dims3 colors Centrifugal pump impeller Design a centrifugal pump impeller: a 90 mm diameter back-plate with a central 12 mm bore and a raised hub, and seven backward-curved blades that sweep from the hub out to the rim, each blade curving smoothly along its path. 10 dims1 color Herringbone planetary gear stage Model a herringbone planetary gear stage at module 1.5: a central sun gear with 18 teeth, three planet gears with 18 teeth each meshing around it, an internal ring gear with 54 teeth, and a carrier plate linking the three planet axles. Color the sun, planets, ring, and carrier differently. 10 dims4 colors 🚀 Quick Start # Clone the repository git clone https://github.com/Adam-CAD/CADAM.git cd CADAM # Install dependencies npm install # Start Supabase npx supabase start npx supabase functions serve --no-verify-jwt # Start the development server npm run dev 📋 Prerequisites Node.js ^20.19.0 or >=22.12.0, with npm 10+ Supabase CLI ngrok (for local webhook development) 🔧 Setting Up Environment Variables 1. Frontend Environment: Copy .env.local.template to .env.local Update all required keys in .env.local: VITE_SUPABASE_ANON_KEY="<Test Anon Key>" VITE_SUPABASE_URL='http://127.0.0.1:54321' 2. Server Environment: Add server-side keys to .env.local, including: ANTHROPIC_API_KEY="<Test Anthropic API Key>" OPENROUTER_API_KEY="<Test OpenRouter API Key>" OPENAI_API_KEY="<Test OpenAI API Key>" GOOGLE_API_KEY="<Test Google API Key>" FAL_KEY="<Test FAL API Key>" SUPABASE_SERVICE_ROLE_KEY="<Test Service Role Key>" BILLING_SERVICE_URL="<Test Billing Service URL>" BILLING_SERVICE_KEY="<Test Billing Service Key>" ENVIRONMENT="local" ADAM_URL="<Adam URL or dev URL>" # Checkout and portal redirect target WEBHOOK_BASE_URL="<Public TanStack App URL>" # Your app URL for /cadam/api callbacks NGROK_URL="<NGROK URL>" # Optional local Supabase Storage tunnel for provider-readable signed URLs 🌐 Setting Up ngrok for Local Development CADAM uses public URLs for provider callbacks and local signed storage URLs: Install ngrok if you haven't already: npm install -g ngrok # or brew install ngrok Start an ngrok tunnel pointing to your TanStack Start dev server: ngrok http 3000 Copy the generated ngrok URL (e.g., https://xxxx-xx-xx-xxx-xx.ngrok.io) and add it to your .env.local file: WEBHOOK_BASE_URL="https://xxxx-xx-xx-xxx-xx.ngrok.io" If a provider must fetch local Supabase Storage signed URLs, run a second tunnel to Supabase and set NGROK_URL to that URL. Ensure ENVIRONMENT="local" is set in the same file. 💻 Development Workflow Install Dependencies npm i Start Supabase Services npx supabase start npm run dev 🛠️ Built With Frontend: React 19 + TypeScript + TanStack Start + Vite 3D Rendering: Three.js + React Three Fiber CAD Engine: OpenSCAD WebAssembly Backend: TanStack Start server routes + Supabase PostgreSQL/Auth/Storage AI: Anthropic Claude API Styling: Tailwind CSS + shadcn/ui Libraries: BOSL, BOSL2, MCAD 🤝 Contributing If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also open an issue. See the CONTRIBUTING.md for instructions and code of conduct. 🙏 Credits This app wouldn't be possible without the work of: OpenSCAD openscad-wasm openscad-playground openscad-web-gui dingcad 📄 License This distribution is licensed under the GNU General Public License v3.0 (GPLv3). See LICENSE. Components and attributions: Portions of this project are derived from openscad-web-gui (GPLv3). This distribution includes unmodified binaries from OpenSCAD WASM under GPL v2 or later; distributed here under GPLv3 as part of the combined work. See src/vendor/openscad-wasm/SOURCE-OFFER.txt. 🌟 Star History Live chart by RepoStars — click for the interactive version. ⭐ If you find CADAM useful, please consider giving it a star! Made with 💙 for the 3D printing and CAD community
Our AI finds products from public sources, then rotates exposure so useful newcomers have a fair chance to be seen.
Learn how discovery works
