Find the Cobalt articles that fit your question. Explore a topic, start with a useful example, or browse every article below.
READ BY TOPIC
A GOOD PLACE TO BEGIN
There is no single US corporate registry. How 50-plus Secretary of State systems work, and how an aggregating API turns them into one integration.
Existence, status, standing, registered agent, and officers: what an entity validation API checks, field by field, and what each field means for underwriting.
Lookup and search are different retrieval operations with different failure modes. Which one your workflow needs, and what each does to your match rate.
Resolve the entity, read the status field, handle slow states, and capture evidence an auditor can replay. The four operations behind one verification call.
Point-in-time rechecks keep filing status current without a monitoring platform. Trigger design, retry mechanics, and when to hand off to continuous detection.
Yes, through registration.updated webhook events. What you still have to build around it, and what no status alert will ever tell you.
Not a like-for-like swap. The Secretary of State layer transfers; watchlist, bankruptcy, TIN and lien monitoring do not. Field mapping and cutover sequence.
Middesk monitors five categories, Cobalt Business Monitoring covers the Secretary of State record only. An alert-type-by-alert-type comparison.
Where an alert lands decides whether it changes anything. The data model for wiring Secretary of State changes into a servicing system.
Start narrow, log before routing, build suppression before alerting. A staged rollout for Secretary of State monitoring across a loan portfolio.