OAuth Integrated Licensing Service
Budget / Salary€30–250
TypeFreelance project
LocationRemote
Posted1 hour ago
Build one purchaser identity and licensing service for these four products. Deliver a functioning Affiliate Rocket OS pilot first. WarriorPlus purchase must grant access automatically; refund must remove it; a purchaser must be able to connect a publicly published ChatGPT plugin to a Rocket account through OAuth. The same account and backend must support the three OTO product permissions later. Do not describe the pilot as ready for sales until a real purchase, refund, OpenAI submission and Free account experience have been demonstrated end to end.
The public plugin is a distribution surface, not the licence. Its MCP tools must require a valid Rocket login and a current product entitlement on each protected call. Put the differentiating paid workflow on the backend; a public skill containing the complete workflow cannot be locked merely by attaching OAuth to a separate tool. Tool output can still be retained by a user after access is revoked. This is access control for future calls, not a guarantee that proprietary methods or generated content cannot be copied.
Use the example hostnames below only after Clive confirms domain ownership. All production URLs must use HTTPS. Scope is a one-time purchase with lifetime access while the sale remains valid, subject to the product's promised terms. There is no subscription billing in this version.
Deliverables
Production and staging Rocket application, source code, deployment instructions, environment configuration, backups and monitoring.
Authenticated Rocket account and activation pages, transactional email, support and admin views.
WarriorPlus IPN ingestion plus sale verification/reconciliation and refund handling.
OAuth 2.1 compatible authorization service (prefer an established provider) and Streamable HTTP MCP service.
Affiliate Rocket OS public plugin package/submission materials, reviewer account and reproducible test cases.
Operator runbook for missed notifications, duplicate sales, refunds, customer email changes, provider outage, and rollback.
The public plugin is a distribution surface, not the licence. Its MCP tools must require a valid Rocket login and a current product entitlement on each protected call. Put the differentiating paid workflow on the backend; a public skill containing the complete workflow cannot be locked merely by attaching OAuth to a separate tool. Tool output can still be retained by a user after access is revoked. This is access control for future calls, not a guarantee that proprietary methods or generated content cannot be copied.
Use the example hostnames below only after Clive confirms domain ownership. All production URLs must use HTTPS. Scope is a one-time purchase with lifetime access while the sale remains valid, subject to the product's promised terms. There is no subscription billing in this version.
Deliverables
Production and staging Rocket application, source code, deployment instructions, environment configuration, backups and monitoring.
Authenticated Rocket account and activation pages, transactional email, support and admin views.
WarriorPlus IPN ingestion plus sale verification/reconciliation and refund handling.
OAuth 2.1 compatible authorization service (prefer an established provider) and Streamable HTTP MCP service.
Affiliate Rocket OS public plugin package/submission materials, reviewer account and reproducible test cases.
Operator runbook for missed notifications, duplicate sales, refunds, customer email changes, provider outage, and rollback.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.