What inputs does save_citation_override accept?

fact_id (string, required): Canonical fact identifier — usually returned in a citation's `fact_ids` array by get_report or any compute tool. Stable across report regenerations. Verified against live SEC data (scoped to `ticker`) before persistence — a fabricated or unresolvable fact_id is rejected. corrected_value (string, required): User-corrected value, stringified. The frontend interprets it based on the fact's known datatype (number, string, ISO date). ticker (string, required): Ticker the fact belongs to (REQUIRED) — scopes fact_id resolution against live SEC data and denormalises the row for fast filtering (the workspace UI's 'my corrections on AAPL' view). source_report_id (string, optional): Optional report id the user was viewing when they applied the correction (provenance). notes (string, optional): Optional free-form rationale, ≤500 chars.

Which Valuein plans include save_citation_override?

Available on the free tier (token required) and on Pro and Institutional. Not point-in-time safe.

Discovery

Save Citation Override

save_citation_override

Benchmark and above

Persist a correction of a citation value. The correction is keyed on the canonical `fact_id` (a stable hash of CIK + accession + concept + period) so it applies to every report that references that same fact — including agent-regenerated reports. Re-saving the same fact_id rep...

Example Call

example_call.pypython

# Using the Valuein MCP server from Python (via MCP SDK)# Or call directly from Claude / Cursor after setup result = await client.call_tool(    "save_citation_override",    arguments={    "fact_id": "EXAMPLE",    "corrected_value": "EXAMPLE",    "ticker": "EXAMPLE"})print(result)

Direct tool call:save_citation_override(...)

Inputs

Parameter	Type	Required	Description
`fact_id`	string	required	Canonical fact identifier — usually returned in a citation's `fact_ids` array by get_report or any compute tool. Stable across report regenerations. Verified against live SEC data (scoped to `ticker`) before persistence — a fabricated or unresolvable fact_id is rejected.
`corrected_value`	string	required	User-corrected value, stringified. The frontend interprets it based on the fact's known datatype (number, string, ISO date).
`ticker`	string	required	Ticker the fact belongs to (REQUIRED) — scopes fact_id resolution against live SEC data and denormalises the row for fast filtering (the workspace UI's 'my corrections on AAPL' view).
`source_report_id`	string	optional	Optional report id the user was viewing when they applied the correction (provenance).
`notes`	string	optional	Optional free-form rationale, ≤500 chars.

Output Fields

overridecreatedcapacity

Example Response

Illustrative

response.jsonjson

{  "override": null,  "created": null,  "capacity": null}

Shape only — field names match the live schema; values are placeholders, not real filings. See MCP server for the structured response shape.

Notes

Available from the Benchmark plan and above.

Try this tool

Get token All tools

CategoryDiscovery

PIT-safeNo

Min planBenchmark

Inputs5 (3 required)

Plan Access

Sample (guest)

Not included

Benchmark (token)

Available

Pro

Available

Institutional

Available

Related Tools

search_companies

Search Companies

get_company_fundamentals

Company Fundamentals

get_valuation_metrics

Valuation Metrics

get_financial_ratios

Financial Ratios

Resources

Point-in-Time methodology →Parquet schema reference →Bulk Data API reference →Python SDK guide →

Index names are trademarks of their owners; Valuein is not affiliated with or endorsed by any index provider.