# Earn with Subs

There are many ways to earn recurring revenue with Subs after you've created your application. The simplest is "personal subs" which allows you to just have a page hosted on Subs and let your users subscribe, nothing more.

## Personal Page

The first thing you need to do is add your app information, and for that, go to [Subs](https://app.subsprotocol.com/#/app/apps), on your apps page click **manage** and complete your app details :&#x20;

<figure><img src="/files/scoaxhtNsZ0MmgSXPKIo" alt=""><figcaption></figcaption></figure>

After that, complete your profile :

<figure><img src="/files/gmwR5tlyENtKlnuShX62" alt=""><figcaption></figcaption></figure>

Boom, the magic of Subs :tada::tada::tada:

<figure><img src="/files/4atFb1VrUS5TGiauqrhN" alt=""><figcaption></figcaption></figure>

#### We keep it simple

<div><figure><img src="/files/log0CGr9ANDuKHjTAyyw" alt="" width="295"><figcaption></figcaption></figure> <figure><img src="/files/FnDVrV4WuL5dx9ZG8HIc" alt=""><figcaption></figcaption></figure></div>

For the end users, they just need to choose the plan and the token they want to use. And, Tadaa, a new subscriber :tada::tada::tada: . Take a look at this [example](https://testnet.subsprotocol.com/#/0x6432BF02a54975500EE3924Dfe504351E27b968B/mumbai_1).

## Subs Widget&#x20;

Another way to earn recurring revenue with Subs is with the Subs widget, which lets you integrate Subs directly into your existing application.

&#x20;      &#x20;

<figure><img src="https://cdn.gamma.app/zjdxhxryph5dzu7/872e7fe83bcc4480a4f623f2e1a84930/original/Capture-d-ecran-du-2023-09-19-10-41-12.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://cdn.gamma.app/zjdxhxryph5dzu7/e4bb8404307b4d618a0eff526d052cb4/original/Capture-d-ecran-du-2023-09-19-09-10-57.png" alt=""><figcaption></figcaption></figure>

Simply install our package JS on your already existing website, it's easy to setup.\
Go check [Subs Widget page](/developer-docs/subs-widget.md).&#x20;

## Telegram Monetization

There are a service build on top of Subs that allow you to monetize your group or channel telegram with your subs plans: Check our [telegram bot](/developer-docs/telegram.md)  .&#x20;

## Discord Monetization

There are others services build on top of Subs that allow you to monetize your discord servers  with your subs plans. Write [us](https://t.me/+esGoPJGnaXE2ODNk) to get access .

## REST API

Do you have a complex existing information system? No problem, our tailor-made API helps you to easily use Subs for recurring revenues.

Our API is incredible for 2 reason:

* Is gas-less, you can add payment to your App and also let your user subscribe for FREE.
* Choose your favorite node provider and you get all the data about your subscription app and customers

It's just here [Subs API](/developer-docs/api.md)

## Directly on-chain

We give you all you need to recreate a mini ABI of our smart-contract.

You can integrate Subs directly into your smart contract if needed, for example verify if a user is your subscriber :&#x20;

```solidity
(bool isMySubscriber,,,) = ISubs(subsAddress).isMySubscriber(appId, userAddress);
```

\
You can even make your own SDK out of it ! Posibilities are endless, there are several possibilities, so it's up to you

All you need: [Subs Contract](/developer-docs/apps-contracts.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.subsprotocol.com/how-it-works/earn-with-subs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
