Where to Publish AI Agents in 2026: Builder's Guide

You can build an AI agent in a weekend. Finding people who will pay to run it is the hard part. Many builders default to GitHub, collect a few stars and call it shipped. A few months later the repo is gathering dust and has earned nothing.

This is a working builder's map of where to publish AI agents in 2026, ranked by what each destination is good at, with a note on who pays whom at each one. The right answer depends on whether you want income, reputation, learning, or all three, and we will be honest about every option, including the platform we operate. Platform rules and fees come from each platform's own pages, read on 12 October 2026 unless another date is given; sources are listed at the end.

The answer in one paragraph

If you want income, publish to an agent marketplace that pays you per run, or to Apify Store if you built a tool that other agents call. If you want reputation, ship to GitHub and Hugging Face. If you want lead flow, publish n8n templates. If you sell to companies, list in the cloud agent stores your buyers already use. If you want several of these, run them in parallel and let the marketplace carry billing and infrastructure.

A common mistake is treating "publish" as one action. Revenue, credibility and discovery each need a different destination: GitHub earns reputation but few transactions, a marketplace earns transactions but little brand surface, and n8n's library earns installs. You do not have to pick one, but you should know what each is doing for you.

The 7 core places to publish an AI agent in 2026

The seven core destinations are GitHub, Hugging Face, the n8n template library, Reddit, Replit, agent marketplaces and your own site. The agent stores and directories that AWS, Salesforce, Google, Microsoft, OpenAI and Anthropic opened in 2025, plus the MCP registries, get their own section because their buyers and payment rails work differently. The comparison is opinionated; effort assumes a polished v1 agent, and the "who pays whom" column reflects each platform's own pages as of October 2026.

Notice what the table makes obvious: no destination gives you a large warm audience, handles billing, covers infrastructure and lets you keep the entire margin. Every option trades one constraint for another, and the rest of this guide is about picking your trade.

Why builders pick the wrong destination

Builders often default to GitHub because that is where they already live. It feels like publishing, yet a repo has no payment rail, no end-user buyer and no way for a non-developer to run the agent. The habit is shipping where you are comfortable instead of where your buyers are, and it shows up in three familiar patterns:

• The "Show HN" launch with no follow-through, aimed at an audience that is mostly not shopping for run-on-demand agents.
• The open-source repo with plenty of stars and no paying users.
• The SaaS landing page built before the agent works, with a Stripe link nobody clicks because there is no traffic.

The fix is to give each of the three jobs its own home:

• Credibility: GitHub or Hugging Face.
• Reach: Reddit, n8n templates, the ChatGPT and Claude directories, and your own social channels.
• Revenue: a marketplace that pays per run, a productized service, or your own checkout once you have warm traffic.

Mixing the three up is how a builder ends up with a popular repo and an empty bank account. Keep them separate, and you can judge each destination on the one job you gave it.

GitHub: best for portfolio, weak for income

Publish on GitHub for trust, contributions and a portfolio that hiring managers and partners can verify, and, since September 2025, for MCP server discovery. Do not publish there for money this month. A repo gives an end user no way to pay to run your agent, and GitHub's two money features have limits:

• GitHub Sponsors charges no fee on sponsorships from personal accounts and up to 6% on those from organization accounts. We would not plan around sponsorship covering an agent's running costs.
• GitHub Marketplace lets anyone share apps for free, but only apps owned by organizations can sell, after publisher verification.

What GitHub is actually good at

Four things, ranked:

1. Proof. A public repo with a clean README, working examples and active issues is the cheapest credibility signal you can ship.
2. Developer distribution. Other builders fork, file pull requests and share good repos in their networks.
3. MCP discovery. The GitHub MCP Registry, launched 16 September 2025, sorts servers by GitHub stars and community activity, so stars now feed discovery for the tools agents use.
4. Downstream pull. A popular repo can turn into freelance work, a hosted version or a marketplace listing that earns.

What GitHub will not do

A repo will not bill end users, host your inference, or reach a non-developer with a task to run. Channels can also close: GitHub deprecated Copilot Extensions on 10 November 2025 in favor of MCP servers. Keep the source on GitHub and the revenue somewhere built for billing, such as a marketplace or a hosted offer. Our guide on how to monetize AI agents covers the wider picture.

Hugging Face: best for research models, weak for end-user agents

Hugging Face is the right home if your agent is built around a custom model, an embedding or a fine-tune. The community there evaluates models technically, and your work gets seen by the right peers. For end-user agent products the fit is weaker: Spaces make good demos, and we found no way to charge users through a Space.

Where it shines

If you have shipped a fine-tune, a quantized model or a novel retriever, Hugging Face is the highest-signal place to publish it. Downloads and likes carry weight in the ML community, and that reputation can turn into job offers, consulting and inbound work. Two features matter for agent builders in 2026:

• Spaces as MCP tools. Any public Space with a visible MCP badge can be exposed as a callable tool in any MCP-compatible client, so a demo can double as a tool agents use.
• Protected Spaces. Since 18 March 2026, PRO and higher accounts can keep a Space's source code private on the Hub while the app stays publicly accessible, so you can demo without open-sourcing.

What a Space costs to host (October 2026)

Hosting depends on the Space type. Hugging Face's docs do not say when the paid-plan rule took effect, so recheck before you budget:

• Static Spaces are free for everyone.
• Gradio and Docker Spaces need a paid plan to create: PRO for personal accounts ($9 a month), Team or Enterprise for organizations.
• Free personal accounts in good standing can still host up to two Gradio Spaces on ZeroGPU.
• The default CPU Basic hardware has no hourly cost; GPU hardware is billed by the hour.

Where it stalls

A typical "AI agent" in 2026 is mostly orchestration, prompts, tools and integrations rather than a custom model, and Hugging Face is not built around that shape. Buyers who want a working agent are rarely browsing Spaces, so treat it as a credibility flag and demo host. The companion piece on AI agent evaluation metrics covers how to demonstrate quality once a model is live.

n8n template library: visibility first, two direct income routes

n8n's official template library is mainly a visibility surface, with two direct income routes on the side. It lists free and paid templates, and n8n staff say paid ones are "fully managed by the seller": you sell through your own checkout link, and n8n does not handle the payment. n8n's Cloud affiliate program also currently pays 30% on referrals for 12 months. We found no sign that n8n pays template authors from the gallery itself.

The library is large: 13,200 workflow automation templates when we read it on 12 October 2026, so a template needs a sharp use case to stand out. n8n's docs also say it is working on a creator program and a template marketplace, with details likely to change, so treat this section as current rather than settled.

The two direct income routes

• Paid templates. List the template in the library and attach your own checkout. One live listing we read (template 4483) sends its buy button to the seller's own PayPal link. Because the seller manages the sale, payment, refunds and support are on you.
• The n8n Cloud affiliate program. Referrals earn 30% for 12 months, calculated on n8n's net earnings for each subscription. Payouts go out monthly once your balance reaches EUR 100, and you need a PayPal account to receive them.

How to make a free template pay off

A free template that solves a recurring pain (lead routing, ticket triage, RAG over a knowledge base) works as an ad for your skills. Treat your author profile as a portfolio that links to your marketplace agents, your repo and a way to book a call, because the conversion happens elsewhere: consulting gigs, custom builds, hosted versions or marketplace listings. A template that never links out gives the work away. For the numbers behind a small agent business, see the economics of bootstrapped AI agents.

Reddit: best for validation, irregular income

Reddit is where you find out whether anyone wants what you are building. Subreddits such as r/AI_Agents, r/n8n and r/SaaS are where operators describe the problem you might solve, often without knowing a solution exists. Searching the past six months of complaints there is the cheapest user research available.

How builders convert Reddit

Reddit's sitewide rules ask you to follow each community's own rules, participate authentically where you have a personal interest, and not spam, so read each subreddit's rules before you post. Within those limits, two patterns are worth trying:

• Comment-first answering. Each week, find a few threads where someone describes your target problem, and write a useful reply that links your agent or repo only when it directly answers the question.
• Build-in-public posts. In our view, a regular progress thread with real numbers (installs, runs, revenue) holds attention longer than a single launch announcement.

What Reddit will not do

Reddit will not produce predictable revenue. Attention there is spiky: one post can bring a burst of interest and then weeks of silence. Use it for validation and reach, and plan your runway elsewhere. For what steadier revenue looks like, the AI agent marketplace complete guide walks through the model.

Replit: good for hosted demos, no native way to get paid

Replit is a solid place to host an interactive demo of your agent and a weak place to earn from it. Whether you build with Replit Agent or by hand, its publishing options (Autoscale, Static, Reserved VM and Scheduled deployments) host your app but give your users no built-in way to pay you. The audience also leans toward developers and learners rather than non-technical buyers who would pay to run an agent on a task.

Two older routes are gone. Replit announced on 23 July 2025 that it was moving its Bounties program to Contra, and replit.com/bounties now redirects there; Replit's templates page returned a 404 when we checked it on 12 October 2026. Any guide that tells you to earn through Replit templates or bounties is out of date.

Use Replit when your agent has an interactive front end people should try without setup. A published Replit app gives you a URL anyone can open, which suits demos and tutorials, since readers skip cloning a repo and configuring environment variables. Discovery beyond the Replit community is modest and billing is up to you, so treat it as a demo channel that feeds your revenue surface. The build vs buy AI agent piece covers when a hosted demo is enough and when you need full productization.

AI agent marketplaces (Gravity and others): best for recurring revenue with less distribution work

Agent marketplaces trade a revenue share for distribution, billing and infrastructure. If you want recurring revenue without becoming a marketer, a billing engineer and a support team, this is the trade that makes sense: a good one pays you per run and puts your agent in front of people who arrived with a task to do. Apify Store and Poe also pay creators directly; their terms are in the next section.

How Gravity's mechanics work

On Gravity, builders earn 21.27% of every run, up to 25% at the top tier, as pure profit. Pure profit means Gravity carries the execution costs, AI inference and infrastructure. Users pick a plan (a free tier, then paid plans from $5 a month during the alpha). For builders there is no listing fee, no paid placement option and no upfront cost to publish. Gravity is in private alpha, and builders apply through the builder alpha; our page for builders has the details.

Ranking is quality-only: no agent climbs because someone paid for placement. For what users pay on the other side, see AI agent pricing in 2026; AI agent marketplace splits compared runs the math on what builders take home after costs.

Who marketplaces are not for

If you already have a large audience and a working checkout, selling direct keeps more margin. For solo builders and small teams, we think the math favors a marketplace, because acquiring users yourself usually costs more than the revenue share. We covered the founder-level version of this in bootstrapping an AI agent platform in 2026.

The big-platform agent stores of 2025 and 2026

Through 2025, AWS, Salesforce, Google, Microsoft, OpenAI and Anthropic opened their own agent stores and directories, and an official MCP Registry launched. Most suit enterprise software vendors and existing SaaS products, and few give a solo builder a simple way to charge per use. The sharpest limit is OpenAI's: its plugin rules allow commerce only for physical goods, so a ChatGPT plugin can bring you users but cannot bill them for a digital service.

Enterprise stores: AWS, Salesforce, Google and Microsoft

These four route buyers through a cloud or CRM account their company already has, after partner onboarding, review or certification:

• AWS Marketplace added AI agents and tools from AWS Partners on 16 July 2025, and listings can show support for MCP and the agent-to-agent (A2A) protocol. Individuals can register as sellers, but paid products need a permanent resident or citizen of an eligible jurisdiction, or a business organized in one. The listing fees in the table have applied since 5 January 2024; server products means AMI, container and machine learning listings.
• Salesforce AgentExchange (4 March 2025) is built into Salesforce and carries actions, prompt templates, topics and agent templates. Salesforce said it launched with more than 200 partners and components that had passed security and customer reviews.
• Google Cloud Marketplace and Gemini Enterprise. Google's 15 October 2025 post says onboarding needs only a link to your Agent Card, a JSON file based on the A2A protocol, and that employees ask their IT administrator to procure agents and add them to the company's Agent Gallery.
• Microsoft 365 Copilot Agent Store (announced 19 May 2025) lists partner agents alongside Microsoft's own Researcher and Analyst. Public distribution runs through Microsoft Marketplace via the Microsoft 365 and Copilot program in Partner Center, after certification and review.

These stores reward builders who already sell to businesses. If A2A or MCP is new to you, our MCP vs A2A vs ACP explainer covers what each protocol does.

Assistant directories: ChatGPT plugins and Claude connectors

The ChatGPT and Codex plugin directory. OpenAI launched apps in ChatGPT on 6 October 2025, saying developers could reach over 800 million ChatGPT users. Its current docs call them plugins, listed in a directory for ChatGPT and Codex, and publishing requires individual or business verification. OpenAI also announced a GPT builder revenue program for US builders in January 2024, but we found no later OpenAI page describing it as live.

The commerce rule is the one to plan around. OpenAI's plugin guidelines say plugins may currently conduct commerce only for physical goods. Selling digital products or services, including subscriptions, digital content, tokens or credits, is not allowed, whether directly or through freemium upsells, and plugins may not display subscription plans, promote upgrades or serve ads. Users can sign in to an existing paid account, so a plugin can send people to a service you bill elsewhere, and it cannot bill them itself.

The Claude Connectors Directory. Anthropic opened it on 14 July 2025. Anyone on a paid Claude plan can submit a remote MCP server through the developer portal at claude.ai/directory/manage; the directory no longer accepts local servers packaged as MCP Bundles, so a local server has to ship inside a plugin to be listed. Anthropic's directory policy, updated 15 April 2026, excludes software that transfers money or executes financial transactions on behalf of users, and software that serves ads. There is no payment rail: the directory brings reach, and your own product does the billing.

Publishing a tool for AI agents: MCP registries

If you built a tool that agents call, usually an MCP server, publishing means getting into the registries that clients read from. Our explainer on the difference between an AI agent and an MCP server covers the distinction. The main routes as of October 2026:

• The official MCP Registry at registry.modelcontextprotocol.io, launched in preview on 8 September 2025. Its maintainers say public sub-registries, such as the MCP marketplaces tied to each client, are free to build on its data.
• The GitHub MCP Registry. GitHub said servers self-published to the open-source MCP Community Registry would appear there automatically.
• The Claude directory and ChatGPT plugins for reach inside those assistants, without billing.
• Apify Store for getting paid per call, covered next.

Two indie marketplaces that pay: Apify Store and Poe

Apify Store pays individual creators directly. You publish automation, AI agent or web scraping projects as paid Actors, priced pay-per-event or pay-per-usage, and receive 80% of revenue, with platform costs coming out of that share; free-plan users are excluded from the calculation. Agentic payments let AI agents run and pay for your Actor without an Apify account, which requires pay-per-event pricing and identity verification (KYC) on your side. For a tool built for agents, it is the closest match we found to a store that bills per call.

Poe runs a creator monetization program that pays bot creators, and part of it lets creators set earnings per message from within the bot's code. Check Poe's eligibility rules and supported countries before you build for it.

Decision framework: pick by your goal

Pick your primary goal first, then layer the other destinations as secondary surfaces. Here is how we would sequence each case.

If your goal is income

Lead with a marketplace that pays a share of every run. Carry a GitHub mirror for credibility, and use n8n templates and Reddit to send people to the marketplace listing. If your agent is a tool other agents call, Apify Store is the paid route. Hold off on your own checkout until the marketplace shows the agent is worth selling at all.

If you sell to businesses

Lead with the store your buyers already procure through: AWS Marketplace, Salesforce AgentExchange, Google Cloud Marketplace or Microsoft's Agent Store. Expect onboarding, review or certification, and for paid AWS listings an eligible jurisdiction or business entity. Add a ChatGPT plugin or a Claude connector for reach, with billing kept in your own product.

If you built a tool for AI agents

Publish the server to the official MCP Registry and keep the source on GitHub so it can surface in the GitHub MCP Registry. Submit it to the Claude directory and as a ChatGPT plugin for reach, and list it on Apify Store if you want to charge per call.

If your goal is reputation

Lead with GitHub and Hugging Face. Ship clean repos, write up the work and contribute to other projects. A marketplace listing adds real-world deployment proof, because reputation compounds faster when you can point to a live, paid version of the work.

If your goal is learning

Lead with Replit and Reddit. Build small things, ship them publicly and let strangers stress-test them; the feedback loop is faster there than on a marketplace where listings move through review. Move winning experiments into a marketplace once they work.

If your goal is all of the above

Run a stack: GitHub for credibility, a marketplace for revenue, Reddit and n8n for reach, Replit for interactive demos, and the MCP registries if you ship tools. Every surface should carry a one-line link to the working version on your marketplace listing, so each one feeds the destination that earns.

What to check before you list anywhere

• Who processes payment: your own checkout (n8n paid templates), the platform (Apify, Gravity), or nobody (the Claude directory).
• What the platform takes: for example, 3% on AWS SaaS public offers, or platform costs out of your 80% on Apify.
• Whether digital goods may be sold: not through ChatGPT plugins.
• Who can sell: paid AWS listings need an eligible jurisdiction or business entity; GitHub Marketplace sales need an organization-owned app.
• Verification: OpenAI requires individual or business verification to publish a plugin; Apify's agentic payments need KYC.
• Platform risk: Replit announced it was moving Bounties to Contra, GitHub retired Copilot Extensions, and n8n calls its creator program ongoing. Keep a way to reach your users that does not depend on one platform.

FAQ

What is the best place to publish an AI agent for income in 2026?

Agent marketplaces that pay a share of every run rank highest for direct income because they handle distribution, billing and execution; for a tool other agents call, Apify Store pays 80% of revenue minus platform costs. GitHub and Hugging Face are better for reputation. n8n's library is mainly for visibility, though you can sell paid templates there through your own checkout.

Can I publish the same AI agent in multiple places?

Yes, with caveats. A common pattern is to keep an open-source scaffold on GitHub for credibility and ship the polished, hosted version to a marketplace for revenue. Avoid identical paid listings across two marketplaces if either has an exclusivity clause in its builder terms.

How much do AI agent builders actually earn on marketplaces?

It depends on demand and on each platform's split. On Gravity, builders earn 21.27% of every run, up to 25% at the top tier, as pure profit because Gravity carries inference and infrastructure costs. On Apify Store you receive 80% of revenue and pay platform costs from it, and on both, usage decides the monthly figure.

Is GitHub a viable place to sell AI agents?

GitHub is excellent for portfolio, contribution and developer discovery, including MCP servers through the GitHub MCP Registry, but a repo cannot bill end users. GitHub Sponsors takes no fee on personal-account sponsorships, and GitHub Marketplace sales are limited to apps owned by organizations. Use GitHub for trust and route monetization to a marketplace or your own hosted product.

Do n8n templates make money?

Free templates do not pay you directly, but they can bring inbound leads for client work. The official library also lists paid templates, which sellers sell through their own checkout, and n8n's Cloud affiliate program currently pays 30% on referrals for 12 months.

Can I sell my AI agent inside ChatGPT?

Only physical goods can be sold through a ChatGPT plugin. OpenAI's guidelines currently forbid selling digital products or services, including subscriptions, digital content, tokens or credits, and forbid promoting upgrades. A plugin can still let users sign in to an existing paid account, so it works as distribution for a service you bill elsewhere.

Where do I publish an MCP server or other tool for AI agents?

Start with the official MCP Registry, which launched in preview in September 2025, and keep the source on GitHub so it can appear in the GitHub MCP Registry. Submit a remote server to the Claude Connectors Directory or package it as a ChatGPT plugin for reach, and list it as a paid Actor on Apify Store to charge per call.

Should I build my own checkout instead of using a marketplace?

Only if you already have an audience. Building checkout, billing, fraud handling, support, and acquisition takes months. A marketplace trades a revenue share for instant distribution and infrastructure. For a first product, distribution beats a higher take rate.

What metrics matter most when picking a publishing destination?

Five things: who pays on that platform, who carries execution cost, whether you may sell digital services there, how ranking is decided, and how fast you get paid. A platform that does not pay you, does not cover inference and ranks by paid placement is a poor place to publish for income.

Sources

All pages accessed 12 October 2026. Dates shown are each page's own publication or update date; undated documentation reflects the page on the access date.

• Microsoft Learn, Copilot Studio documentation on publishing agents to channels (undated): https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-fundamentals-publish-channels
• Google Cloud documentation, "Host AI agents on Cloud Run" (undated): https://docs.cloud.google.com/run/docs/ai-agents
• GitHub Docs, GitHub Sponsors fees: https://docs.github.com/en/sponsors/getting-started-with-github-sponsors/about-github-sponsors
• GitHub Docs, GitHub Marketplace for apps: https://docs.github.com/en/apps/github-marketplace/github-marketplace-overview/about-github-marketplace-for-apps
• GitHub Blog, GitHub MCP Registry announcement, 16 September 2025 (updated 18 September 2025): https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/
• GitHub Changelog, deprecation of GitHub Copilot Extensions (GitHub Apps), September 2025: https://github.blog/changelog/2025-09-24-deprecate-github-copilot-extensions-github-apps/
• Hugging Face Docs, Spaces overview (undated): https://huggingface.co/docs/hub/spaces-overview
• Hugging Face, Pricing: https://huggingface.co/pricing
• Hugging Face Docs, Spaces as MCP servers: https://huggingface.co/docs/hub/spaces-mcp-servers
• Hugging Face Docs, Spaces changelog (protected Spaces entry, 18 March 2026): https://huggingface.co/docs/hub/spaces-changelog
• n8n Community, staff reply on template types, 10 April 2025: https://community.n8n.io/t/97080
• n8n Community, staff reply on seller-managed paid templates, 25 May 2025: https://community.n8n.io/t/119845
• n8n, template 4483 listing: https://n8n.io/workflows/4483-linkedin-post-automation-with-ai-gpt-4o-generation-and-slack-approval/
• n8n Docs, Templates: https://docs.n8n.io/workflows/templates/
• n8n, workflow template library: https://n8n.io/workflows/
• n8n, Affiliate program: https://n8n.io/affiliates/
• Reddit Inc., Reddit Rules (Rule 2): https://redditinc.com/policies/reddit-rules
• Replit on X, Bounties program moving to Contra, 23 July 2025: https://x.com/Replit/status/1948085191534334433
• Replit Docs, About deployments: https://docs.replit.com/cloud-services/deployments/about-deployments
• Salesforce, AgentExchange launch press release, 4 March 2025: https://www.salesforce.com/news/press-releases/2025/03/04/agentexchange-announcement/
• AWS What's New, AI agents and tools in AWS Marketplace, 16 July 2025: https://aws.amazon.com/about-aws/whats-new/2025/07/ai-agents-tools-aws-marketplace/
• AWS Marketplace Seller Guide, listing fees (effective 5 January 2024): https://docs.aws.amazon.com/marketplace/latest/userguide/listing-fees.html
• AWS Marketplace Seller Guide, seller eligibility: https://docs.aws.amazon.com/marketplace/latest/userguide/user-guide-for-sellers.html
• Google Cloud Blog, "Scaling AI agents with Google Cloud Marketplace and Gemini Enterprise", Oliver Schulz, 15 October 2025: https://cloud.google.com/blog/topics/partners/google-cloud-ai-agent-marketplace
• Microsoft 365 Blog, Build 2025 announcements, 19 May 2025: https://www.microsoft.com/en-us/microsoft-365/blog/2025/05/19/introducing-microsoft-365-copilot-tuning-multi-agent-orchestration-and-more-from-microsoft-build-2025/
• Microsoft Learn, "Choose how to publish and distribute your plugin" (undated): https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/publish
• OpenAI, "Introducing apps in ChatGPT", 6 October 2025: https://openai.com/index/introducing-apps-in-chatgpt/
• OpenAI Developers, plugin submission: https://developers.openai.com/apps-sdk/deploy/submission
• OpenAI Developers, plugin guidelines: https://developers.openai.com/plugins/plugin-guidelines
• OpenAI, "Introducing the GPT Store", 10 January 2024: https://openai.com/index/introducing-the-gpt-store/
• Anthropic, Claude connectors directory announcement, 14 July 2025: https://www.anthropic.com/news/connectors-directory
• Claude Docs, submitting a connector to the directory: https://claude.com/docs/connectors/building/submission
• Anthropic, Software Directory Policy (updated 15 April 2026): https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy
• Model Context Protocol Blog, MCP Registry preview, 8 September 2025: https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/
• Apify Docs, monetizing your Actor: https://docs.apify.com/platform/actors/publishing/monetize
• Apify Docs, pricing and costs: https://docs.apify.com/actors/publishing/monetize/pricing-and-costs
• Poe Creator Docs, creator monetization (undated): https://creator.poe.com/docs/resources/creator-monetization