Starter vs Pro

EasyClaw V3 splits capabilities between Starter and Pro. This page explains the product story so you know what to expect in Telegram and the dashboard. Prices and line-item entitlements are always authoritative on checkout; your live usage envelope is in Dashboard → Usage.

What the tiers are for

Starter is the daily-driver tier: reminders, questions about your connected context, RSS and Calendar-backed automations, and Telegram-native habits. Pro adds integration and monitoring surfaces that cost more to run safely at scale: HTTP fetch, inbound webhooks, and richer web-style monitoring where the product enables them.

How gating works

When a feature needs Pro, the dashboard and runtime enforce it before expensive work starts. Trials often mirror Starter-class guardrails so you can evaluate the product without burning open-ended browser budgets.

Starter — what you get

• Telegram-first usage: reminders, Q&A, follow-up-style nudges within fair use.
• Google Calendar and RSS as the primary recurring data sources for many automations.
• Daily Control and template-style briefings when Calendar is connected.
• Monitoring patterns that lean on feeds rather than heavy browsing.

Pro — what unlocks

• HTTP / API fetch inside automations for machine-to-machine data pulls.
• Inbound webhooks so external systems can POST events into EasyClaw.
• Broader monitoring options where the UI exposes web-style or scheduled search flows (subject to budgets).

When to pick which

• Choose Starter if your wins are calendar + RSS + Telegram discipline.
• Choose Pro if you need push or pull HTTP glue between systems you already operate.

Examples

• Starter: “Summarize this RSS every morning” + “Daily control at 7am with my meetings.”
• Pro: “POST CI status to my inbound webhook” + “Fetch internal JSON before summarizing for the team.”

Limits (without stale numbers)

Token caps, per-run budgets, and fair-use envelopes change as the product evolves. Do not trust static numbers in third-party screenshots — open Usage in your dashboard and read the current checkout copy before buying.

Common mistakes

• Assuming every chat message can spin up unlimited browser sessions — runs are budgeted.
• Expecting webhook or fetch features on Starter — see HTTP fetch and Inbound webhooks.

Related

• Integrations overview
• Troubleshooting
• FAQ (we are aligning marketing FAQ with these docs over time)

Next step: compare plans on checkout, then wire your first integration from Get started.