Notte APInotte.cc ↗
Access Notte's subscription plans, per-unit usage rates, plan-level rate limits, and blog posts via two structured endpoints. No auth setup required.
What is the Notte API?
The Notte.cc API exposes 2 endpoints covering Notte's own platform data: current pricing plans and blog content. The get_pricing endpoint returns a full snapshot of all subscription tiers — including per-plan credits, features, and rate limits — alongside per-unit usage rates for resources like browser sessions and proxies. The list_blog_posts endpoint returns posts with titles, dates, authors, and category metadata, filterable by category.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/cb8fff52-f512-4314-9994-919fa651f93e/get_pricing' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace notte-cc-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Notte SDK — bounded, re-runnable; every call capped."""
from parse_apis.notte_cc_api import Notte, BlogCategory, NotteError
client = Notte()
# Fetch current pricing snapshot
for plan in client.pricings.get(limit=4):
print(plan.name, plan.price, plan.highlighted)
# List engineering blog posts
for post in client.blog_posts.list(category=BlogCategory.ENGINEERING, limit=3):
print(post.title, post.date, post.author)
# List all recent posts and pick one
post = client.blog_posts.list(limit=1).first()
try:
detail = client.blog_posts.list(category=BlogCategory.PRODUCT, limit=1).first()
print(detail.title, detail.slug)
except NotteError as e:
print("error:", e)
print("exercised: pricings.get, blog_posts.list")
Retrieves Notte's complete pricing information including subscription plans (Free, Developer, Startup, Enterprise), per-unit usage rates, and per-plan rate limits. Returns a single snapshot of the current pricing page.
No input parameters required.
{
"type": "object",
"fields": {
"plans": "array of plan objects with name, description, price, credits, features, and highlighted status",
"rate_limits": "array of operational limits broken down by plan tier",
"usage_rates": "array of per-unit usage pricing items (e.g. browser sessions, proxies)"
},
"sample": {
"data": {
"plans": [
{
"name": "Free",
"price": "$0",
"credits": "$10 credits",
"features": [
"Credits cover - Sessions, proxies, LLMs, functions",
"Browser concurrency - 5",
"Session duration - 15 min"
],
"description": "Try the full platform without a card.",
"highlighted": false,
"credits_note": "Granted once. No expiry."
},
{
"name": "Developer",
"price": "$20/mo",
"credits": "$20 credits / mo",
"features": [
"Browser concurrency - 25",
"Agents / functions - 25 concurrent",
"Session duration - 120 min"
],
"description": "For prototypes and early production workloads.",
"highlighted": false,
"credits_note": "Monthly credits expire each cycle."
},
{
"name": "Startup",
"price": "$100/mo",
"credits": "$100 credits / mo",
"features": [
"Browser concurrency - 100",
"Agents / functions - 100 concurrent",
"BYO - Keys, proxies",
"Session duration - 300 min"
],
"description": "For teams scaling browser agents in production.",
"highlighted": true,
"credits_note": "Monthly credits expire each cycle."
},
{
"name": "Enterprise",
"price": "Custom",
"credits": "Custom credits",
"features": [
"Browser concurrency - Custom",
"BYO - Keys, Proxies, Cloud",
"More - SSO, SLAs, HIPAA"
],
"description": "For custom limits, compliance, and support.",
"highlighted": false,
"credits_note": "Commercial terms matched to usage."
}
],
"rate_limits": [
{
"free": "5",
"limit": "Browser concurrency",
"startup": "100",
"developer": "25",
"enterprise": "Custom"
},
{
"free": "5",
"limit": "Agents / functions concurrency",
"startup": "100",
"developer": "25",
"enterprise": "Custom"
},
{
"free": "5",
"limit": "Vaults",
"startup": "200",
"developer": "50",
"enterprise": "Custom"
},
{
"free": "5",
"limit": "Personas",
"startup": "200",
"developer": "50",
"enterprise": "Custom"
},
{
"free": "15 min",
"limit": "Max session duration",
"startup": "300 min",
"developer": "120 min",
"enterprise": "Custom"
},
{
"free": "No",
"limit": "Bring your own keys",
"startup": "Yes",
"developer": "No",
"enterprise": "Yes"
},
{
"free": "No",
"limit": "Bring your own proxy",
"startup": "Yes",
"developer": "No",
"enterprise": "Yes"
},
{
"free": "Included",
"limit": "Captcha solving / stealth",
"startup": "Included",
"developer": "Included",
"enterprise": "Targeted"
},
{
"free": "No",
"limit": "On-premise deployment",
"startup": "No",
"developer": "No",
"enterprise": "Available"
}
],
"usage_rates": [
{
"item": "Browser sessions",
"price": "$0.05 / hour"
},
{
"item": "Browser functions",
"price": "$0.05 / hour"
},
{
"item": "Residential proxies",
"price": "$10 / GB"
},
{
"item": "LLM tokens",
"price": "Token price"
},
{
"item": "Free credits",
"price": "$10 once"
},
{
"item": "Monthly plan credits",
"price": "$20 or $100 / mo"
},
{
"item": "Manual top-ups",
"price": "Available"
}
]
},
"status": "success"
}
}About the Notte API
Pricing and Plan Data
The get_pricing endpoint returns a single snapshot of Notte's current pricing page. The response includes a plans array where each object carries a plan name, description, price, credit allocation, feature list, and a highlighted flag indicating which plan is currently featured. Alongside plan data, the response includes a rate_limits array broken down by tier and a usage_rates array listing per-unit costs for individual resources such as browser sessions and proxies — useful for estimating costs before committing to a plan.
Blog Content
The list_blog_posts endpoint returns posts from the Notte blog in reverse-chronological order. Each post object includes title, slug, url, date, category, excerpt, author, and image_url. The optional category parameter filters results to a specific blog category; omitting it returns the most recent posts across all categories. There is no pagination parameter — the endpoint returns a flat posts array for the available results.
Coverage Scope
Both endpoints reflect Notte's own platform rather than third-party sources. get_pricing is a point-in-time snapshot and will reflect whatever pricing Notte currently publishes. Blog post freshness depends on how recently the endpoint was last fetched, so time-sensitive monitoring of new posts should factor in polling frequency.
The Notte API is a managed, monitored endpoint for notte.cc — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when notte.cc changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official notte.cc API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor Notte plan pricing changes over time by polling
get_pricingand diffing theplansarray - Programmatically compare per-unit
usage_ratesfor browser sessions and proxies across plan tiers - Build a cost estimator that reads
rate_limitsandusage_ratesto project monthly spend - Aggregate Notte blog content into a developer newsletter or documentation digest using
list_blog_posts - Filter Notte blog posts by
categoryto surface only relevant technical or product-update content - Track new blog post authors and publication dates via the
authoranddatefields in post objects
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Notte have an official developer API?+
What does the `get_pricing` endpoint actually return beyond plan names and prices?+
plans (with name, description, price, credits, features list, and highlighted status per plan), rate_limits (operational limits broken down by plan tier), and usage_rates (per-unit pricing for individual resource types like browser sessions and proxies). This gives a complete picture of both subscription-level and consumption-level costs in one call.Can I filter blog posts by author or date range?+
list_blog_posts endpoint currently supports filtering by category only. Author and date-range filtering are not exposed as parameters, though each returned post object does include author and date fields that you can filter client-side. You can fork this API on Parse and revise it to add server-side author or date filtering as an endpoint parameter.Does the API expose individual blog post body content, not just excerpts?+
list_blog_posts endpoint returns metadata fields — title, slug, url, date, category, excerpt, author, and image_url — but does not return the full post body text. You can fork the API on Parse and revise it to add a get_blog_post endpoint that fetches full article content by slug.How fresh is the pricing data returned by `get_pricing`?+
get_pricing will reflect those changes. For change-detection use cases, store previous responses and diff against new ones rather than assuming data is static.