Schema library finance
Return a venture portfolio record from a public page.
Pass this JSON Schema and a public source URL to/extract/json. Normalize public portfolio-company entries from a venture firm’s site.
TEXT
MARKDOWN
LINKS
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 venture portfolio record.
Venture capital or investment firm portfolio page listing companies and investment details.
| Field | Type | What it holds |
|---|---|---|
firm_name | string, required | Name of the investment firm. |
firm_domain | string, required | Primary domain of the investment firm. |
firm_type | string | Type of investment firm. |
investment_stages | array | Stages of investment the firm participates in. |
geographic_focus | array | Geographic regions the firm focuses on. |
sector_focus | array | Industry sectors the firm focuses on. |
fund_size_usd | number | Size of the current or most recent fund in USD. |
founding_year | number | Year the firm was founded. |
managing_partners | array | List of managing partners at the firm. |
portfolio_companies | array, required | Companies in the firm's portfolio. |
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.
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.
import schema from './vc-portfolio-page.json'
const res = await client.extract.json({
url: 'https://example.com/pricing',
json_schema: schema,
})tabstack extract json 'https://example.com/pricing' \
--schema @./vc-portfolio-page.jsonAdaptation
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
Related schemas
Other schemas in this category.
- Same category: alternative asset listing.
- Same category: angel & seed deal.
- Same category: crypto asset.
- The job rather than the object: the Extract API.