ASI:One vs Poe

ASI:One

The idea worth taking seriously is routing: rather than one model trying to do everything, ASI:One plans the task and delegates steps to agents published on Agentverse, so capability grows with the marketplace rather than with the next training run. Making it OpenAI-compatible is a smart adoption shortcut — your existing client works after a base-URL change. What is missing is commercial clarity: no price list, no rate card, and a consumer pitch that promises far more than the developer docs demonstrate.

Pros

• +OpenAI-compatible API, so existing SDKs, LangChain and MCP-era tooling connect with a base-URL swap
• +Three model sizes — asi1-mini, asi1 and asi1-ultra — behind one interface
• +Models plan multi-step work and delegate to specialist agents rather than answering alone
• +Backed by Fetch.ai and tied into its existing Agentverse agent marketplace
• +Documented integration paths for Claude Code, Cursor and LangChain

Cons

• −No pricing of any kind is published — not per token, not per plan
• −The marketing site renders as an empty JavaScript shell to anything but a browser
• −Several documented doc paths return 404, so the reference material is incomplete
• −Answer quality depends on third-party agents on Agentverse, whose reliability is not vouched for
• −No country or legal entity for Fetch.ai is stated on either site

Poe

Poe makes sense if you want to compare frontier models side by side without paying each vendor, and the custom-bot layer is a cheap way to publish a prompt as a product. The catch is the points meter: one subscription buys wildly different quantities of use depending on which bot you pick, and per-bot costs are Poe's to change, so the plan you buy is not necessarily the plan you keep.

Pros

• +One subscription spans models from several vendors plus image and video generators
• +Custom bots can be built from a prompt and shared or monetised
• +Apps on web, iOS, Android, Mac and Windows
• +A creator API exists for developers

Cons

• −Points pricing makes real capacity hard to predict across models
• −Per-bot point costs and allowances are set by Poe and change over time
• −The home page blocks automated access and the subscription page shows regional prices, so USD figures could not be confirmed from the vendor
• −No team or enterprise tier is visible

Does ASI:One or Poe have a free tier?

Poe has a free tier; ASI:One prices on request.

Which has a public API, ASI:One or Poe?

Both ship a public API, so either can be built on; the fact table above shows the platforms each one runs on.