Naver Blog Search
Native Naver Blog relevance results through the existing ScrapeBadger provider. Up to 100 source rows from at most five source pages, start 1–1000, with query-bound cursor continuation. Preserves Korean, source calendar days and unknown dates; does not invent exact publish timestamps. Date sorting and AI enrichment are unsupported. Empty or fully filtered windows are free.
post plus compatibility fields title, link, description, bloggername, bloggerlink and postdate. Korean text is preserved; highlight tags are stripped and entities decoded. The provider supplies calendar days or relative labels, so post.published_at remains null. Exact calendar days appear in post.ext.published_date with published_at_precision: "day"; relative/unknown dates remain null. Views, likes, comments and author verification are unknown, not zero.
Use display or limit (1–100; default 10), with start (1–1000), or return next_cursor alone. Matching aliases must agree. A cursor binds the query, requested size and inclusive since/until calendar-day filters for one hour. Conflicting explicit values are rejected. Date filtering excludes rows without a known date, and pagination advances over scanned source rows even when every row is filtered out.
Each source page contains up to 30 rows; a requested window uses at most five bounded parallel source reads. Within a response, duplicate post IDs are removed and counted in dropped. Rankings can change across requests: the two live source pages overlapped on 13 of 30 IDs. Deduplicate by post.id across pages. The source does not supply a reliable total, so total is null. Full source pages may lead to an empty terminal page. Traversal stops at source position 1,000; cursors are not snapshots or an exhaustive collection guarantee.
Known production limitation: both audited 100-row requests failed because the provider repeated an entire later page. These requests were rejected with HTTP 502 and refunded. Smaller windows and first/second-page continuation passed. Large-window and deeper-pagination reliability are not certified; do not assume that the accepted 100-row/1,000-offset bounds establish working coverage.
Only sort=sim and judgments=off are supported. Date sorting, AI relevance/fit/labeling, dry runs and synthesis are rejected with an unbilled 422. These remain feature-parity gaps.
A fresh nonempty result costs 1 credit. Errors, empty/fully filtered windows, cache hits and successful idempotent replays cost zero. Use X-Max-Credits: 1. All source reads are reserved against the shared 500-credit ScrapeBadger verification ceiling before any request starts; up to five pages use up to 25 provider credits. Missing/exhausted budget state fails closed. Requests have a 45-second shared timeout and a 2 MiB per-page bound. This approved verification allowance is not a permanent production capacity commitment; no purchase or top-up is enabled.Authorizations
Headers
Optional nonnegative integer cap on the maximum request hold. A live request whose hold exceeds this cap returns 422 CREDIT_BUDGET_EXCEEDED before spending. Metered holds use the requested limit; cache hits and successful idempotent replays cost zero.
x >= 0Query Parameters
Korean or other search text, up to 500 characters; alternatively supply a returned cursor.
Requested source rows, 1–100 (default 10). Both aliases must agree. Duplicate/date filtering can reduce returned_count.
1 <= x <= 100One-based source offset, 1–1000. Cursors preserve remaining source positions.
1 <= x <= 1000Only sim (native relevance order) is supported by this provider; date is rejected.
sim Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
score, filter Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Only off is supported; no AI synthesis or scoring is performed.
off Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
1 Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
goal Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
Unsupported by the current native-blog adapter; supplying this parameter returns an unbilled 422.
1 Inclusive YYYY-MM-DD calendar-day filter within the scanned window. Rows with unknown dates are excluded when either bound is supplied.
Inclusive YYYY-MM-DD calendar-day filter within the scanned window. Rows with unknown dates are excluded when either bound is supplied.
Opaque one-hour next_cursor; can be used alone. Binds query, requested size and date filters; explicit conflicts are rejected.
Requested source rows, 1–100 (default 10). Both aliases must agree. Duplicate/date filtering can reduce returned_count.
1 <= x <= 100Response
Native Naver Blog relevance results through the existing ScrapeBadger provider. Up to 100 source rows from at most five source pages, start 1–1000, with query-bound cursor continuation. Preserves Korean, source calendar days and unknown dates; does not invent exact publish timestamps. Date sorting and AI enrichment are unsupported. Empty or fully filtered windows are free.
x >= 0The selected operation determines the resource fields in this object. Source data can omit a metric or report it as null.