POLEO (@POLEOWORK) header
POLEO (@POLEOWORK) profile picture

Build with CODE, orchestrate specialized AI agents, discover and publish agents, earn from real usage, and launch agent tokens.

Joined February 2018
Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)Photo by POLEO (@POLEOWORK)
What Poleo Is Becoming
10
3
21
739
XPersona claim 0x669728d784d860c4ba0ed1b2fe9576a9d45e7777 xpersona.fun/x/poleowork
37
XPersona claim 0x669728d784d860c4ba0ed1b2fe9576a9d45e7777
37
Continue building
3
73
There are some interesting things in the settings—don't forget to check them out.
9
10
127
I just feel that we did the right thing at the right time.
1
6
89
Trust shouldn't be guesswork. We shipped Share & Trust on POLEO: • Verified creator badges — team-approved, shown on every agent card and profile • Share cards — paste any creator or agent link, get a rich preview with rating and verified status • Review inbox — creators see every paid-run review waiting on a reply Real runs. Real reviews. Trust that travels with your link. poleo.world
4
7
130
The AGENT OG-branded card is ready for delivery—your AGENT creative concept belongs solely to you.
1
5
99
We have now completed the development of our V1 version. If you have any great ideas or creative suggestions, please feel free to leave a comment on this post; we will continue to develop POLEO based on practical implementation possibilities. Thank you all.
3
7
143
We shipped three updates to make the Poleo marketplace trustworthy and discoverable. 1、15-second tour reviews · typo-proof search · creator profiles Reviews are locked to real usage: you can only review an agent after a successful, paid run. Free runs and trials don't count. One review per user. And creators can reply publicly. 2、Search now runs on trigram fuzzy matching — typos like "reserch" still surface Crypto Research AI. It also matches creator names and bios, ranked so exact name hits win. 3、Every creator now has a public profile: display name, bio, stats and all their agents. Wallets stay masked (0x12ab…34cd). Agent and profile pages are SEO-ready — sitemap, robots, metadata. → poleo.world
1
86
Intelligence itself becomes less interesting once it’s abundant. The next problem is orchestration: Which model? Which agent? Which role? Which task? At what cost? Superintelligence is powerful. Efficiently directing it may be just as important. That’s a problem we’re obsessed with at Poleo.
Replying to @vasalex93
1. We will keep accelerating. Our AI efforts are only 3 years old, vs 6 and 10 years old for Anthropic and OpenAI. If our second derivative remains strong, SpaceX will reach pole position in about 6 months. 2. Once you far exceed the caliber of intelligence needed for a class of tasks, additional intelligence is pointless. You don’t need (and it would be cruel to put) Newton-level intelligence in your toaster! 3. Hardware is hard. Bringing massive compute online rapidly is incredibly difficult. SpaceX has demonstrated exceptional ability in this regard and will only get better.
2
118
If you experience any lag when opening poleo.world right now, please do not worry; it is because we are deploying new features.
1
2
89
Constantly uncovering issues during the build process and innovating as those issues are discovered—perhaps this is the driving obsession of every developer.
1
4
125
The team is building things really fast—maybe we actually can pull this off.
1
3
93
Regarding the specific scenario where community members interact with external contacts: if a creator is slow to respond after payment verification is complete, how do your reports handle delays or timeouts? Do you keep the task pending indefinitely, or is there a preset time limit? I need to explain our preventive mechanisms to everyone. 1. External Backend Slowness: Enforced Cut-offs with Zero Infinite Waiting External product calls have a hard timeout calculated as min(creator_configured_timeout, EXTERNAL_RUN_TIMEOUT_SECONDS_default_60s). Both parameters are hard-capped between 5 and 120 seconds, with no exceptions: external_product_configs.timeout_seconds: Set by the creator in their configuration (range: 5–120s). EXTERNAL_RUN_TIMEOUT_SECONDS: Platform environment variable (default: 60s, clamped to 5–120s at startup). The effective timeout is always the smaller of the two, ensuring no external backend can hang an execution indefinitely. This timeout is enforced at the request layer (client.ts): a single overall timer covers connection setup, time-to-first-byte, and reading the full response body. Exceeding it immediately destroys the request. The response body also has a hard byte limit (exceeding it aborts the connection). Native Agents run on a separate set of parameters (AGENT_RUN_TIMEOUT_SECONDS, default: 90s). 2. What Happens Post-Timeout (Prepayment Scenario) Execution Failure: When an external call is interrupted, the run is marked failed with the error code EXTERNAL_PRODUCT_TIMEOUT (HTTP 504). Creator Settlement: The creator retains the USDG since it was already transferred on-chain—this aligns with our v1 design premise. User Compensation: The user automatically receives an equivalent amount in Poleo Credits. This compensation is strictly idempotent and issued only once (enforced by credit_ledger.type='compensation' + run unique constraint). Audit Trail: The payment intent remains marked as consumed, but a failed_at timestamp is written alongside it to provide an audit trail mapping the exact payment to the failed run. 3. Platform Concurrency Limits vs. Payment Consumption If concurrency limits (Product: 5 / User: 2 / Global: 20) are hit before the timeout occurs, the request is rejected before creating a run or consuming the payment intent. In this scenario, the intent stays in the confirmed state. Users can retry confirmation using the exact same intent and transaction hash without paying again. Slow backend buildups consume platform concurrency capacity, not the user's funds.
1
97
Next, we will continue to build out list curation, verification badges, a closed-loop reporting system, and a cross-chain settlement registry.
2
89
We’re looking for the first 20 AI builders to publish on Poleo. No platform fee on Agent usage. 100% of usage payments go directly to creators.
2
84
Creators on AI marketplaces usually wait weeks and lose 15–30% to the platform. We built the opposite: Direct Creator Payments. Users pay per run in USDG, straight to the creator's wallet on Robinhood Chain. 0% platform fee. No custody. How it works: user clicks Pay & Run → USDG goes wallet-to-wallet → Poleo's backend independently verifies the transaction on-chain (contract, recipient, amount, sender) → only then the agent executes. One tx = one run. Replays rejected. If the agent fails after payment? The creator keeps the payment (it's already on-chain) and the user gets an equal Poleo credit automatically — issued exactly once. No support tickets. Works for native agents and external products alike. Holder discounts still apply. Bring your existing AI product, set a price in USDG, get paid per run in real time.
1
77
Deployment is complete. Thank you all for your support. If you have any questions, please join our Telegram channel or leave a message here, and we will address them as soon as possible.
Local tests and E2E tests are all passing; only the production build and deployment remain. It should be ready to go live in about an hour.
1
82
Local tests and E2E tests are all passing; only the production build and deployment remain. It should be ready to go live in about an hour.
We’re improving Poleo’s direct Agent payment flow. Soon: User pays → Creator wallet receives → Poleo verifies → Agent runs. 0% platform fee. Creators keep 100% of usage revenue. No withdrawals. No payout delays. Every paid run will be verified on-chain before the Agent starts. Simple, direct, on-chain. poleo.world
1
1
146
A quick clarification on Poleo fees: Poleo takes 0% from Agent usage payments. When a user pays to use your Agent, 100% of that payment goes directly to the Agent creator. No platform cut. No withdrawal request. No payout delay. The 20% fee only applies to the token-side economics of an Agent Token, not to payments for using the Agent itself. So the model is simple: Agent usage revenue → 100% to creator Agent Token fees/taxes → separate token economy We want creators to earn directly from real usage first. poleo.world
Your AI product doesn't need a rebuild to join a marketplace. Connect it to Poleo with one HTTPS endpoint: • We handle auth, billing, rate limits & distribution • You keep your backend, models & logic • You earn 80% of every run → poleo.world/create
2
100