--- title: "Approximate weighted-average entry price for a CUSIP across 13F holders" method: GET path: "/api/v1/sec/13f/consensus/{cusip}/avg-entry-price" tags: ["Hedge Fund Intelligence"] --- # Approximate weighted-average entry price for a CUSIP across 13F holders `GET /api/v1/sec/13f/consensus/{cusip}/avg-entry-price` ## Request - Base URL: `https://sugra.ai` - URL: `https://sugra.ai/api/v1/sec/13f/consensus/{cusip}/avg-entry-price` - Auth: API key in header `x-api-key` Derived cost-basis approximation per fund and portfolio-wide. 13F filings disclose position SIZE per quarter-end, NOT transaction-level cost basis. This endpoint reconstructs an estimate by multiplying each fund's positive quarterly Δshares by that quarter's average daily close (Sugra Finance equity price feed). Sales are EXCLUDED - their basis cannot be unambiguously attributed without transaction-level disclosure. `ticker` query param is REQUIRED in v1 (CUSIP -> ticker resolver is a follow-up item). Each response carries an explicit `methodology` string and a per-fund + portfolio `confidence` tag - consumers must surface those to end users; the number is an estimate, not a tax cost basis. ## Path parameters - `cusip` string, required: 9-character canonical CUSIP. ## Query parameters - `ticker` string, required: Ticker symbol used to fetch per-quarter average daily close (required: the CUSIP is not yet resolved to a ticker). - `from_quarter` string, nullable: Oldest stem in window. Default: oldest stem in retention manifest. - `to_quarter` string, nullable: Newest stem in window. Default: newest stem in retention manifest. ## Response `200` Per-fund + portfolio weighted-avg entry price for one CUSIP. - EnvelopeSec13fAvgEntryPrice - `data` Sec13fAvgEntryPrice, required: Approximate cost basis for one CUSIP across all 13F holders. Reconstructed from quarter-to-quarter position deltas multiplied by the quarter's average daily close. The cost basis is NOT disclosed in 13F filings; this is a derived approximation with explicit methodology and confidence cues attached. Sales (negative deltas) are excluded - they cannot be unambiguously attributed under FIFO vs LIFO without transaction-level disclosure. - `comparison` Sec13fComparison: The interval a comparison actually covers. The baseline quarter is chosen from what retention holds, not from the calendar, so when a quarter is missing the two compared quarters are not adjacent and the delta spans more than one. Without this block the response would describe six months in the words of three. - `from_period_end` string, nullable: Reported quarter-end of the baseline. - `to_period_end` string, nullable: Reported quarter-end of the target. - `quarters_apart` integer, nullable: How many quarters the comparison covers; 1 is quarter-over-quarter. Null when the interval cannot be determined. - `calendar_adjacent` boolean, nullable: Whether the two quarters are consecutive. Absent when the interval could not be determined - false would read as a known answer. - `skipped_quarters` string[], nullable: Reported quarter-ends lying between the two that this comparison does not cover. - `note` string, nullable: Present only when quarters were skipped. - `cusip` string, required - `ticker` string, required: Caller-supplied symbol used for quarter price lookup. - `issuer` string, required: Issuer name from the 13F filing (first seen in window). - `from_quarter` string, required: Oldest stem effectively used. - `to_quarter` string, required: Newest stem effectively used. - `quarters` Sec13fQuarterAvgPrice[], required: Per-quarter price snapshots used in the weighted-basis calculation, oldest -> newest. - `stem` string, required: 13F quarter stem (e.g. `2025q4` or `01dec2025-28feb2026`). - `quarter_start` string, required: Inferred quarter start (ISO YYYY-MM-DD). - `quarter_end` string, required: Period-end date from the manifest (ISO YYYY-MM-DD). - `avg_close_usd` number, nullable: Arithmetic mean of daily closes in the quarter range; null if upstream returned no bars. - `sample_days` integer: Daily bars used to compute the mean. 0 when upstream returned no candles. - `available` boolean, required: Whether the price was usable for weighted-basis aggregation. - `methodology` string, required: Plain-English description of the cost-basis approximation: 'Σ(Δshares × quarter_avg_close) for positive deltas only; sales excluded; daily close arithmetic mean per quarter range'. - `portfolio` Sec13fAvgEntryPortfolio, required: Portfolio-wide weighted aggregation across all funds in the window. - `total_acquired_shares` integer, required - `weighted_avg_entry_price_usd` number, nullable: Aggregate weighted basis across all funds. Null when no acquisitions priced. - `confidence` string, required: `high|medium|low|none` per same heuristic as per-fund confidence. - `funds` Sec13fAvgEntryFund[], required: Per-fund breakdown sorted by total_acquired_shares descending. - `cik` string, required: 10-digit zero-padded SEC EDGAR CIK. - `manager_name` string, required - `current_shares` integer, required: Holder's share count at `to_quarter`. 0 if the fund exited the position by `to_quarter`. - `total_acquired_shares` integer, required: Sum of positive quarterly position deltas (acquisitions only) across the window. - `quarters_acquired` integer, required: Number of quarters with a positive Δshares contribution. 0 when no acquisitions in window. - `weighted_avg_entry_price_usd` number, nullable: Σ(Δshares × quarter_avg_close) / Σ(Δshares). Null when no acquisitions in the window, or when every acquisition quarter had no available price. - `confidence` string, required: Heuristic quality tag: `high` (>=3 priced acquisition quarters), `medium` (2 quarters), `low` (1 quarter), `none` (0 quarters with usable price). - `meta` SugraMeta, required: Metadata on a /api/v1/* response envelope built through `helpers.response.sugra_response`, which is how routes are expected to answer. A route that assembles its own `meta` dict carries only the keys it writes itself, so an optional field below can be absent because this response has nothing to report OR because that route does not build its envelope here - the two are not distinguishable from the outside. - `endpoint` string, required: Requested endpoint path. - `data_time` string, required: ISO 8601 timestamp the data on this response is stamped with. It is the source's own timestamp whenever the source supplied one this API could read; when it did not, this field falls back to the value of `response_time` and `data_age_days` is omitted, so the PRESENCE of that field is the signal to read - with the one exception named in its own description, a route that substitutes its own current time for a source timestamp it never received. Usually UTC (`Z`), but a source stating its own numeric offset keeps it (2026-04-16T14:30:00+09:00) rather than being converted a second time. For a source that publishes by period this is the period's START (see `period`) and for one that publishes by calendar day it is that day's midnight - in neither case a moment at which anything was observed or released. - `response_time` string, required: ISO 8601 UTC timestamp when this response was produced. - `provider` string, required: API name and version. - `data_age_days` number, nullable: Age of the data in days at the moment this response was produced, i.e. `response_time` minus `data_time`. Present ONLY when the timestamp this response is stamped with is a clock time that could be read as a real instant. It is ABSENT - never 0 - in every other case. Absent when no readable source timestamp was supplied, because `data_time` then repeats `response_time` and a zero age would assert that the data is current precisely where its true age is unknown. Absent when the source names a calendar day, a month, a quarter or a year (see `period`): the instant is then a boundary this API anchored at midnight, and time since a day or a quarter BEGAN is a different quantity from the age of the data - a daily series is out by up to a day, a quarterly one by up to a quarter. A midnight counts as such a boundary whichever zone it is stated in, and whether the source stated it or this API anchored it. The one case this field cannot see is a route that substitutes its own current time for a source timestamp it never received: the substituted value is a real, readable instant and is indistinguishable from one the source stated, so the age reads as roughly 0. The shared cache-and-fetch helper behind most routes stopped doing that, but the presence of this field is a statement about the timestamp the response carries, not a guarantee about the route that supplied it. Rounded to 0.001 day (86.4 seconds), so 0.0 is a real measured age anywhere within roughly +/-43 seconds and not a stand-in for unknown; a source stamping an instant in the future reports a negative value (-0.001 or less) rather than being clamped. Sources publish on very different cadences, so a non-zero age is normal, not an error. Preserve absence in client code: a generated client that materialises a missing optional number as its numeric default turns 'age unknown' back into 'age zero', which is the exact confusion this field exists to remove. - `source` string, nullable: Identifier of the primary upstream source used for this response. - `attribution` string, nullable: Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response. - `fallback_used` boolean, nullable: True when the primary source failed and a fallback produced the data. - `fallback_chain` string[], nullable: Ordered list of sources attempted, in the order they were tried. - `cached` boolean, nullable: True when this response was served from the internal cache. - `stale` boolean, nullable: True when the response is known stale under its source freshness policy, or when a cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data. - `stale_since` string, nullable: ISO 8601 UTC timestamp of the last good copy this response was served from. Present only when stale is true. - `period` string, nullable: Unit of observation, when the source publishes by period rather than by instant. `data_time` carries the period's START instant so it stays machine-readable; this field preserves what that instant used to mean, which the conversion would otherwise erase. Present only for such sources, and only when the source hands the API the label itself - a client that converts the period to its start instant before building the envelope loses the label, though not the age exclusion, which is decided by the instant. Note that `data_age_days` is omitted whenever this is present, because an age measured from a period start is not a freshness figure. - `notes` string, nullable: Data-quality caveat about THIS response - how old the underlying report is, a chokepoint AIS lower-bound, or that a source-reported `data_time` could not be read and the response time is shown instead. Distinct from `attribution`, which is a licensing obligation. Multiple caveats are joined with ' | '. Present only when there is one. ## Other responses - `401`: Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401. - `422`: Validation Error - `429`: Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window. - `500`: This API answered a shape its own schema refuses. Typed body `error: response_shape_invalid`. Stays a 500. Not an upstream failure. - `503`: Upstream source is temporarily unavailable. Retry after a short delay. ## Changes > 45 revisions in range; 1 not diffed. - **2026-09-13** `d2472ec2cf81`: 1 info - added the non-success response with the status `500` - **2026-09-09** `4f8853a61440`: 1 info - added the optional property `meta/stale_since` to the response with the `200` status - **2026-09-01** `328d061c12ca`: 3 info - added the optional property `meta/data_age_days` to the response with the `200` status - added the optional property `meta/notes` to the response with the `200` status - added the optional property `meta/period` to the response with the `200` status - **2026-08-20** `652554d2aae1`: 1 info - added the optional property `data/comparison` to the response with the `200` status - **2026-08-08** `4c4530760ba1`: 12 info - added the optional property `code` to the response with the `401` status - added the optional property `code` to the response with the `429` status - added the optional property `code` to the response with the `503` status - added the optional property `hint` to the response with the `401` status - …8 more [Operation history](https://skmtc.dev/sugra/apis/sugra-api/changes/api/v1/sec/13f/consensus/:cusip/avg-entry-price/get.md) --- [API](https://skmtc.dev/sugra/apis/sugra-api.md) · [All operations](https://skmtc.dev/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc.dev/sugra/apis/sugra-api/revisions/62345201d043?raw)