Schema library b2b-intel

Return a SaaS pricing record from a public page.

Pass this JSON Schema and a public source URL to/extract/json. Return plan names, displayed prices, billing periods, and stated features from a public pricing page.

Use this schema The JSON file

tabstack.ai/pricing

TEXT

MARKDOWN

LINKS

extract.tsTypeScript

const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: {
    type: 'object',
    properties: {
      plan: { type: 'string' },
      price: { type: 'number' },
    },
  },
})

res = client.extract.json(
    url='https://example.com/pricing',
    json_schema={
        'type': 'object',
        'properties': {
            'plan': {'type': 'string'},
            'price': {'type': 'number'},
        },
    },
)

tabstack extract json https://example.com/pricing \
  --schema '{"type":"object","properties":{"plan":{"type":"string"},"price":{"type":"number"}}}'

What it captures

Fields in this SaaS pricing record.

Schema for SaaS product pricing page data including plans, features, and pricing models.

Field	Type	What it holds
`company_name`	string, required	Name of the SaaS company.
`company_domain`	string, required	Website domain of the company.
`pricing_model`	string	Primary pricing model used.
`free_tier_available`	boolean	Whether a free tier or free plan is available.
`free_trial_available`	boolean	Whether a free trial is offered.
`trial_days`	number	Number of days in the free trial.
`billing_intervals`	array	Available billing intervals (e.g., monthly, annual).
`annual_discount_percent`	number	Discount percentage for annual billing.
`currency`	string	ISO 4217 currency code for pricing.
`custom_pricing_available`	boolean	Whether custom or enterprise pricing is available.
`plans`	array, required	List of pricing plans available.
`page_title`	string	Title of the source page. Tabstack auto-fills this from page metadata when left empty.
`favicon`	string	Favicon URL of the source page. Tabstack auto-fills this from page metadata when left empty.

Example

Inspect and validate the response shape.

The example below is generated from the schema to demonstrate its structure. Edit the object or paste a real response to validate it in your browser.

What it checks

Pass or fail, and the first reason why.

Whether the text parses as JSON, whether the top level is an object, and whether each field the schema requires is present at the declared type. A null is allowed anywhere. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

Example data, not a live response.

Usage

Send the schema with your source URL.

The schema travels with the request rather than living on your account, so the same call can send a trimmed version for one page and the full one for another. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

saas.tsTypeScript

import schema from './saas-pricing-page.json'

const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: schema,
})

tabstack extract json 'https://example.com/pricing' \
  --schema @./saas-pricing-page.json

Adaptation

Make the schema match your application.

The schema is a starting point, not a guarantee that every source page contains every field. Three things are worth doing before you write one into your system, and the schema-authoring guide covers the rest.

Remove what you do not need

A shorter schema is a smaller response and fewer fields to handle.

Describe the ambiguous ones

A description tells Extract what to look for when a label could mean two things.

Validate before you store

Check the returned object against the schema rather than trusting it.

Related schemas

Other schemas in this category.

Same category: api documentation endpoint.
Same category: company profile.
Same category: competitor profile.
The job rather than the object: the Extract API.