Continuation of #7 — SDK v1.41 parity + Monitors

[nikhil-mat]

Continuation of #7.

SDK: context.dev v1.41.0

New:

• Monitors resource — 11 operations: create, get, update, delete, run, list, listAccountChanges, listAccountRuns, listChanges, listRuns, getChange
• SDK sync 1.34 → 1.41 across brand, web, AI, industry, utility
• Nested request objects: pdf, viewport, enrichment, markdownOptions
• New web params: colorScheme, country, numResults, scrollOffset
• webhook.secret (monitor create + update)
• AI specific_pages; extractProducts directUrl variant; datapoint_object_schema
• Full enums: ticker_exchange (72), force_language (120)
• Per-operation param scoping corrected
• Numeric bounds aligned to SDK (timeoutMS ≥ 1000, viewport 240–7680 / 240–4320)
• 268 → 379 tests
• lint-clean (n8n-nodes-base)

[nikhil-mat]

Pushed an update that takes this from SDK-parity to full API coverage.

Tracks the API as of context.dev v2.12.0 (2026-08-18).

Coverage: 36 → 53 operations, 6 → 9 resources

Resource	Ops
Monitors	15
Brand Intelligence	9
Web Extraction	9
Web Scraping	7
Batch	6 (new)
Utility	3
People	2 (new)
News	1 (new)
Parsing	1 (new)

Also added: POST /brand/retrieve, GET /brand/search, monitor credit-usage, monitor limits, retrieve-a-monitor-run, and webhook secret rotation.

Parameter coverage: tags across every operation that accepts it, plus zdr, settleAnimations, actions, includeHTML, dedupe, clearPopups, and the nested pdf / viewport options. POST /parse is supported as a raw binary upload.

WebDBs is left out for now, since the published SDK doesn't expose it — happy to add it once it's public.

Breaking changes

Operation values and resource names change — aiDataExtraction → webExtraction, NAICS/SIC move under Web Extraction, and the brand operations regroup. Existing workflows need reconnecting. The credential name contextdevApi is unchanged, so saved credentials keep working.

Verification

npm test runs lint and build. The node is lint-clean and eligible for n8n Cloud verification.

A live conformance suite ships in tests/live/. It assembles requests from the built node's own routing in dist/, so a green run is evidence about the published artifact rather than a parallel client:

CONTEXT_DEV_API_KEY=... npm run test:live

All read-only operations pass against the live API (33/33 on a paid-plan key; prefetch and people-enrich return a plan-gated 403 otherwise, which the suite treats as an allowed result). --include-mutating adds create/use/delete lifecycles for monitors and batches, covering the operations that need an existing record id.

Every request carries an n8n-live-test tag so suite traffic stays separable from real usage in the dashboard. CI runs the suite when an API key is available and skips it on forks.

Tests

The 246 structural assertions are removed. They restated the API by hand and had already drifted from it — the brand routing table predated POST /brand/retrieve — and duplicated checks the linter and compiler already make. Behaviour is now verified against the real API instead.

Also

Adds the LICENSE file package.json declared but didn't ship.

Two things worth a look on the API side, both hit while testing:

• POST /batch/submit — the documented request example uses input.type / data.type, but the schema and the server require input.mode / data.format. Coding from the example gives a 400.
• DELETE /batch/{batch_id} — documented, but returns 403 "The API you have tried to access does not exist". Cancelled batches stay listed as a result.

cc @nikhilrado