Agents can think and act. Now they can notice.

An event stream for code and AI agents. It collects facts from official registers, journals and public feeds (new companies, tenders, insolvencies, property auctions, vulnerabilities; connected accounts such as DMs and reviews are planned) and delivers each one in the same standard format, so an agent can act the moment something happens. It is operated by Yumankind OÜ in Tallinn, Estonia, and is in early access.

One fact about the world, in one standard shape: a company was registered, a tender was published, an auction was scheduled. Each event has a stable id, a type, where and when it happened, the companies involved, a typed payload and a link to the source record.

New companies in the UK, Spain, France, Ireland, Norway, Finland, Switzerland, Latvia, Estonia, Lithuania, Poland, Czechia, Slovakia, Israel and four US states (New York, Colorado, Connecticut and Oregon), with closures, relocations, capital increases and business sales where the register publishes them; insolvency proceedings in the UK and France; US private funding rounds; public tenders and contract awards in 42 European countries, the UK included, and every contract on Portugal’s national portal, below the EU thresholds too; public property auctions in Spain; new alcohol and business licences in Texas, New York, Chicago and Missouri; US layoff notices from five states; FDA medical device clearances; job ads and hiring surges in Sweden; worldwide, every new CVE, the ones exploited in the wild, open-source security advisories and new exploits; outages on twenty status pages and Google Cloud; new releases on PyPI and crates.io; new AI models, price changes and retirements; new US trade mark applications; and data breach notices filed in Washington State. The event catalogue marks every type as ready or planned, and demand decides what comes next.

Yes. GET /api/events?types=company.registered&country=FR returns, with your access key, new companies from the official register or gazette of that country, newest first, as standard events with the company’s name, legal form and, where the source has them, share capital, purpose and industry code. Ask for several countries at once with country=GB,FR,ES. The UK, Spain, France, Ireland, Norway, Finland, Switzerland, Latvia, Estonia, Lithuania, Poland, Czechia, Slovakia, Israel and four US states are live. See the docs.

Yes. GET /api/events?types=procurement.tender_published returns tenders from the EU’s public procurement journal for 42 European countries, the UK included, plus the UK’s own tender service and Portugal’s national contracts portal (weekly), with buyer, CPV codes, estimated value and deadline. Contract awards are procurement.contract_awarded.

Live today: new companies in the UK, Spain, France, Ireland, Norway, Finland, Switzerland, Latvia, Estonia, Lithuania, Poland, Czechia, Slovakia, Israel and four US states; insolvencies in the UK, France, Estonia, Lithuania and Slovakia; sanctions-list changes (US, UK, EU); product recalls (US, Canada, EU); new laws, regulations and consultations (EU, US, UK, NL, ES, DE, IT) and enforcement actions; new restaurants and food shops (UK, Norway, France, New York City, Chicago); power outages and day-ahead prices in Europe; public tenders in 42 European countries; US funding rounds, SEC current reports, federal grants, building permits, licences, layoff notices, trade marks and device clearances; job ads in Sweden; property auctions in Spain; and the whole world for vulnerabilities, outages, package releases, new MCP servers, platform deprecations, end-of-life dates and AI models. Our research maps 1,550 sources in 104 countries; see coverage.

Through the ws command line tool (it runs a program or starts an agent for each event or batch, or writes JSON files to a folder), the live stream (Server-Sent Events), polling the events API, signed webhooks, or the remote MCP server. All of them are live, with the access key you get once you’re in; see the docs.

Treat events as untrusted data: they carry text from the outside world, and some of it can try to give your agent instructions. Run the agent that reads them in a sandbox with no credentials and only the tools it needs, have it return structured output, and keep a person approving anything that leaves your systems. See safety in the docs.

Yes. vulnerability.published carries every new CVE with its CVSS score, weaknesses (CWE) and affected vendors and products; vulnerability.exploited fires when a vulnerability is confirmed exploited in the wild, with its fix deadline and whether ransomware uses it. Filter by severity in your code, or let an agent check the affected products against your inventory. Vulnerabilities are always free, on every plan: they never count toward your monthly events and are never locked.

Yes, without any email: the agent runs npx worldsignals signup, which makes an account of its own with a key on its device. Then it either gives you a payment link for its own plan (agent accounts have no free plan), or shows a code you approve, signed in, at worldsignals.dev/link, so it acts for your account with your plan until you revoke it. See agent accounts.

Sign up with your email and open the link we send you: it confirms your address. Work emails get in as soon as they confirm. Personal addresses (Gmail, Outlook…) join the waiting list, as the free plan is by invitation, and we email you when you’re in; or skip it by upgrading to a paid plan from the console. Once you’re in, the link signs you in and shows your key. Lost it? Sign in again and open your Account page. The key reads collected events through the API, the live stream, webhooks, the MCP server and the command line.

Public events come from official registers and journals, used under their reuse licences, with attribution on every event. Paid data is passed on only where its licence allows redistribution; otherwise you connect your own key and those events go to you alone. Private events come only from accounts you connect. We deliver data; we don’t resell what we may not.

Events are about companies and public bodies. We leave people’s names out where the source allows it, and mark any event that identifies a person. Private events from connected accounts (planned) will be visible only to you.

The free plan costs nothing and needs no card. It includes 2,500 events a month, counted on every delivery (the API, the live stream, webhooks and MCP); past them, events still arrive but locked, showing their type, country and time, and webhooks wait, until the next month or an upgrade. Vulnerabilities (CVEs) are always free and don’t count. Paid plans (Developer, Team and Business) add real time and more events; sign up before 8 December 2026 and keep 30% off any of them for life, for as long as your subscription stays active.

So it stays for people, not bots. Personal addresses (Gmail, Outlook…) join the waiting list, and we send invitations from it and to our followers on social media. Company emails skip the list: you’re in as soon as you confirm. And anyone can skip it with a paid plan.

Yes. After you sign up, the stream builder has a “Something else?” field. Requests from members decide the order we build in.

Yes, on the Business plan. We build custom event types and the sources behind them for your use: your industry’s registers, a set of sites or documents you care about, signals combined across sources, or your own systems. They arrive in the same standard format, private to you. Talk to us.