Paquets
Chercher un paquet
246 paquets, du catalogue du site, chacun lu dans son dépôt. Un mot se cherche dans le nom, la famille, la description et les mots-clés.
Tenu dans les fichiers catalog/ du site, lus dans chaque dépôt : 25 familles, 180 fournisseurs, 241 paquets avec un manuel.
246 paquets
-
omnibase: entities, view models, contracts, forms and helpers for any PHP host; under Symfony with omnibridge/symfony, under Laravel with omnibridge/laravel, persisted through omnibridge/doctrine
-
Omniauth: who signs in, and by which factors, under any PHP host - the contracts (accounts, the stores of each proof, the second-factor rule, the host's small duties), the conductor (begin, then verify; the attempt, the result), the methods that need no library (password through symfony/password-hasher, sign-in link, code by e-mail, backup codes, trusted devices in scheb/2fa's cookie format), the sign-in through identity providers (Omniauth\OAuth\: state, PKCE and nonce, the linking by the provider's subject, the sign-up of an unknown identity; each provider a package of its own, omniauth/google first), PSR-14 events and Testing helpers. WebAuthn (passkeys) and one-time passwords (TOTP) are packages of their own; the Symfony and Laravel bridges live in omnibridge.
-
Omnibank: one contract for bank access - accounts, balances, transactions, transfers, consents and webhooks - over statement files and bank APIs, and its Symfony bundle (Omnitrade's sibling for banking).
-
Omnibill: one contract for transmitting and receiving electronic invoices - submit a conformant file (Factur-X, UBL, CII), follow its lifecycle statuses, receive suppliers' invoices, declare a status, look a company up in the directory, transmit e-reporting - whoever carries it: an e-mail (omnibill/email), an approved platform's standard API XP Z12-013 (omnibill/afnor), Chorus Pro (omnibill/chorus-pro); and its Symfony bundle.
-
Omnibus: one contract for parcel carriers - rates, labels, tracking, pickup points - and its Symfony bundle (the Payum of shipping).
-
Omnidns: a domain name where it is registered, under any PHP host - whether it is free and at what price, registering and renewing it, the account's domains and their terms, their name servers, and the records of their zones; from OVH, Gandi, Cloudflare or Scaleway through one set of models. Providers are packages of their own (omnidns/ovh, omnidns/gandi, omnidns/cloudflare, omnidns/scaleway); no framework in require.
-
Omnidocs: one model of a manual, whatever wrote it - Markdown, Sphinx, Doxygen, JSDoc: its versions, its pages (title, contents, headings, the file to edit), its API entries and their anchors, read through one source contract; a search index a static page searches, and the HTML conventions of symfony.com/doc (callouts, versionadded, code with captions and tabs) every format renders to.
-
Omnidrive: one contract for reading and writing files wherever they are kept - a directory of this machine, an S3 bucket, an SFTP (SSH) or FTP server - by the name the application gives each storage; Flysystem is the engine behind it, never in its signatures.
-
Omnifood: one contract for the restaurant platforms - delivery orders (Uber Eats, Deliveroo, Just Eat) and table reservations (TheFork, Zenchef) - their menus, their stores, their webhooks, and its Symfony bundle.
-
Omnifund: who funds a project, read under any PHP host, wherever the funding is received - the profile (backers counted, income, goal), the sponsors and the tiers offered, from GitHub Sponsors, Open Collective or Liberapay. Providers are packages of their own (omnifund/github-sponsors, omnifund/opencollective, omnifund/liberapay); no framework in require.
-
Omnilab: one contract for the public science-data APIs - entities (a compound, a gene, a protein, a species, a star, an earthquake) with their properties, units and cross-references, series (a variable measured at a place over time: weather, climate, air) and catalogued products (a satellite scene, a dataset, STAC-like) - whatever the domain; a Collector that follows cross-references from one base to the next, and a Symfony bundle.
-
Omnilex: one contract for the sources of law - texts, codes and case law, searched with filters (jurisdiction, date, subject, type), read in the version in force at a date, their links followed, what is new listed - from Légifrance, Judilibre, EUR-Lex and the French administrative courts' open data; identifiers (ECLI, NOR, CELEX, pourvoi, Légifrance) normalised and validated; and its Symfony bundle.
-
Omnimap: maps under any PHP host, whoever draws them - one description of a view (centre, zoom, markers) that a provider's driver draws in the browser, the provider's image of it made on the server, geocoding over geocoder-php, and the map cache: the picture of a view, signed, cut in tiles, kept in a storage of the host's and served from it, captured by the browser or made by the server. Providers are packages of their own (omnimap/google, omnimap/openstreetmap); the Symfony and Laravel bridges live in omnibridge.
-
Omnimeet: one contract for video meetings - open a room, let a participant in (a JavaScript engine and its options, an embedded frame, or an address), close it, read its state, hear the provider's callbacks - whatever carries the call: the two browsers themselves (omnimeet/direct) or a conferencing service (omnimeet/jitsi); and its Symfony bundle.
-
Omniplay: games under any PHP host, behind contracts by capability. On the stores: a game's record (texts, dates, studios, platforms, price, pictures, scores, identifiers on other stores), a search by title, a player's library and whether a player owns a game, read only. Online play, whatever the game's engine or netcode: a fleet of game servers kept by their heartbeats, a player seated on a fitting server with a short-lived signed ticket the server checks by itself, hosting providers that start and stop servers, a player's identity verified by their platform. Providers are packages of their own (omniplay/steam, omniplay/gog, omniplay/itch, omniplay/igdb, omniplay/rawg, omniplay/docker, omniplay/edgegap, and inside the game server omniplay/dotnet, mirror, netcode, godot and node); the ticket's format and its vectors are documented for a server in any language; the Symfony and Laravel bridges live in omnibridge.
-
Omnipost: the social networks' family. Publish: one contract for publishing a post - a reel, a picture, a carousel - through a network's API, reading one's own feed, and the capabilities each network imposes. Share: plain share links for visitors (Facebook, X, Pinterest, LinkedIn, Bluesky, Mastodon, Threads, WhatsApp, Telegram, Reddit, e-mail, copy, share sheet) - no network script, no cookie, one JSON for Twig, Blade and React. And its Symfony bundle.
-
Omnireach: what outside tools know of a site's audience, under any PHP host - search queries, pages and positions from the search engines (Search Console, Bing Webmaster Tools), visitors, entry pages and sources from the analytics tools (Matomo, Plausible, Google Analytics 4), one query and one report whoever answers; a taken-over site's history over any period. Providers are packages of their own (omnireach/search-console, omnireach/bing-webmaster, omnireach/matomo, omnireach/plausible, omnireach/ga4); the Symfony and Laravel bridges live in omnibridge.
-
Omnireview: what customers say of an establishment elsewhere - its rating, its reviews, replying as the establishment, inviting a customer to review, the link to leave one - whoever hosts them: Google (omnireview/google), Tripadvisor (omnireview/tripadvisor), Trustpilot (omnireview/trustpilot), each platform's terms of display and caching declared; and its Symfony and Twig bridges, which always show the origin, the date and the link.
-
Omnischolar: one contract for a researcher's publications - author profiles, works, books and their editions, citations - read from OpenAlex, HAL, Crossref, ORCID, Open Library, arXiv and INSPIRE, merged and deduplicated, exported as BibTeX, RIS or CSL-JSON; and its Symfony bundle.
-
Omnisearch: search the way Doctrine is for SQL, whatever the engine - indexes declared on the classes by attributes (#[Index], #[Field]), connections and drivers, requests and responses (DBAL), a manager, finders, queries, results and objects loaded back, the indexing rule (ORM); an in-memory engine, a Doctrine bridge and a Symfony bundle. Engines are packages of their own (omnisearch/typesense).
-
Omnishield: one contract for guarding a form - is this token valid (a captcha: ALTCHA, Turnstile, reCAPTCHA), is this content spam (Akismet), are this address, this e-mail, this name known for abuse (StopForumSpam, disposable e-mail domains) - whoever answers; and its Symfony bridge: a form field, a constraint, the ALTCHA challenge's route, a Twig function.
-
Omnisign: one contract for having documents signed - create an envelope (documents, signers, fields, a level: simple, advanced, qualified), send it, follow it, remind, cancel, sign in the application's page, download the signed documents and their evidence, hear the provider's webhooks - whoever signs: Yousign (omnisign/yousign), DocuSign (omnisign/docusign), a DocuSeal instance (omnisign/docuseal); and its Symfony bundle.
-
Omnisong: one contract for listening to a musician's catalogue - releases, tracks, previews, the links to every platform with the label first, and the embeds that play from them - and its Symfony bundle.
-
Omnistate: one contract for what states and registries know - companies, VAT numbers, domains and networks (the Omnipay of public registers).
-
Omniticket: tickets sold elsewhere, read and checked under any PHP host - the events a ticketing service sells (dates, rates, places left, sold out, where to buy), who comes (attendees), and whether a ticket code is valid at the door, one contract whoever sells them. Providers are packages of their own (omniticket/weezevent, omniticket/billetweb, omniticket/helloasso, omniticket/eventbrite, omniticket/ticketmaster); the Symfony and Laravel bridges live in omnibridge.
-
Omnitrade: one contract for payment providers and commerce platforms - purchase, authorize, capture, refund, webhooks, platform orders - and its Symfony bundle (Omnibus's sibling for trade).
-
A Composer plugin that knows no package: the patches and the stub providers the installed packages declare in extra.omnibridge, applied after install and update, restored when they no longer apply, recorded with checksums and checked in CI.
-
The storage glue of omnibase sites, framework-free: Doctrine reading the structure described outside of it (omnisense/omnibridge's Omnibridge\Schema), the naming strategy that turns their entities into their tables, the UTC date types, and an entity manager built with them, for any framework reading the same database; and omnibase's persistence on Doctrine (Omnibridge\Doctrine\Omnibase\: its repositories, finder compiler, mapping, DBAL types, walkers, filters and listeners), which omnisense/omnibase requires.
-
omnibase's entities on Eloquent's database layer, framework-free: illuminate/database (Laravel's connection, or Capsule outside Laravel) reading the tables omnisense/omnibridge's Omnibridge\Schema describes into the same plain PHP entities Doctrine maps - a data mapper: tables from the description, a hydrator with PHP 8.4 lazy ghosts and lazy collections, an identity map, casts; and omnibase's persistence on Eloquent (Omnibridge\Eloquent\Omnibase\: its backend, scopes, repositories and finder compiler) when omnisense/omnibase is installed.
-
The Laravel host of omnisense/omnibase: its Foundation contracts (urls, translations, locales, access, parameters with the database settings laid over Laravel's config, clock, events...) answered by Laravel's services and seeded in Base\Contract\Runtime, the persistence through omnibridge/eloquent or omnibridge/doctrine, Twig through omnibridge/twig, and the pieces an omnibase page asks of its framework (Encore tags, the app variable, simple forms).
-
A page of a site as a React component and its props, the same from any framework: the first visit an HTML shell holding the page, a visit within the site the page in JSON (header X-Omnibridge), the JavaScript side rendering it and following the site's links without reloading.
-
The static host of the omnibridge family: a generic exporter that enumerates an application's addresses (explicit lists, a router's #[Route] routes with the values of their parameters, a sitemap), renders each at build time by the application's own code (its host's request handling, its actions, or any callable), and writes a deterministic folder for a static host or a CDN - HTML pages, the files of an asset manifest (Vite, Webpack), the files the pages refer to, redirections, 404.html, sitemap.xml and a report with checksums and diagnostics (broken links, duplicate outputs, missing assets, non-deterministic pages). No framework, no bundler.
-
The Symfony host of omnisense/omnibridge's contracts (urls, translations, access, sessions, tokens, environment) - adapters over Symfony's router, translator, security and kernel, their container wiring and OmnibridgeBundle - and the framework packages omnisense/omnibase no longer requires. A Symfony site requires it beside the core.
-
The Twig side of omnibridge: the contract a page rendered with Twig asks of any framework (path, url, asset, trans - omnisense/omnibridge's Urls and Translations), the Twig extension that provides it where the framework does not, and helpers.
-
The core of the omnibridge family: the contracts any host answers for an application that runs on more than one framework (addresses, translations, languages, access, sessions, tokens, stored files, routes, environment) and the registry the application reaches them through. No framework, no ORM: each omnibridge/<host> bridge answers them with its host's services.
-
Administration backoffice for base-bundle: dynamic CRUD, dashboard, menus and field-based form generation
-
Concert dates and venues for omnibase: an Event is a Thread; the agenda page, ICS feeds and imports, Google Calendar links, JSON-LD MusicEvent.
-
Chronicles and visitors' comments for omnibase: a Post is a Thread, a Comment is read by Akismet before it goes online.
-
A broadcast's site on omnibase: a programme, its episodes, what was played on stage (performances), the songs and who sang them - on omnibase/video's films and omnibase/music's performers.
-
A teacher's open classroom for omnibase: levels and subjects, learning sequences and their sessions, idea cards, resources to download (free, for members, or sold through omnibase/marketplace).
-
The cookie answer of every omnibase site, in one place: a small circle, a panel, the features the visitor answers for and what each keeps, a countdown, on @glitchr/flowjs/cookie.
-
Consulting for omnibase: an independent professional's services (Offering) presented on their site, the quote request on omnibase's contact model with its notice, kept and answered from the back office; the rules an offering keeps that a site or a profession adds; the hook for hours paid through omnibase/marketplace's Credit.
-
The documentation, read from Markdown files: a manual in the back office, and public manuals - one per package, read in its repository, one version per branch - with a search (Typesense, or the pages' own index).
-
The drive application for omnibase: a site's own cloud of folders and files - who each folder is for, sharing by name, workspaces with their tasks, search, previews, zips, download counts - on the site's storage or its Google Drive
-
Property management for omnibase: organisations, buildings and units, associates, leases and tenants, rent calls, receipts and online payment, contractors and work orders, invitations and a private space for each - posting to omnibase/ledger
-
A FAQ for omnibase: questions by section, answered in the back office, and the form to ask another.
-
Software forge for base-bundle: releases built from git tags, free and licensed downloads, a private Composer repository, client projects with a shared board, prepaid support hours and quotes - paid through base-bundle-market
-
Discussion forum for base-bundle: categories, topics built on Thread (tags, followers, likes), markdown posts, moderation and admin CRUD
-
Albums of photographs for omnibase: an Album is a Thread, its Photos are ordered, one album is one creation.
-
The health regime on omnibase/office: a practice (multi-professional, nursing, physiotherapy...), its practitioners read from the RPPS, patients and their dependants, home care requests, fees, results sent through the encrypted vault, medical secrecy in who may read what, the emergency banner, GDPR export.
-
The lawyers' regime on omnibase/office: a law firm's site within article 10 of the RIN - the domain name checked (10.5), specialisations from the certified list only and three dominant fields at most (10.2), wording checked against comparison, the fees and the mandatory fee agreement (11.1, 11.2), the consumer mediator of the profession, the memo of what is declared to the Ordre; fields of practice, the client's space on the encrypted vault, professional secrecy in who reads a document; the hook for paying fees online.
-
Double-entry accounting for omnibase: books, a French chart of accounts, journals, parties and lettering, bank feeds through omnisense/omnibank, reconciliation with ranked suggestions, trial balance, general ledger, income statement, balance sheet and the FEC export
-
The legal professions on omnibase, one bundle and a profile for each: a lawyer's firm (the RIN's article 10 - domain name, certified specialisations, fees and their agreement, the declaration to the Ordre), a notary's office (regulated tariff and discounts, addresses in notaires.fr, the declaration to the chamber, the profession's charter), a jurist (nothing the law of 31 December 1971 reserves to a regulated profession). In common, on omnibase/office: fields of practice, a first appointment asked without an account, the client's space on the encrypted vault, who of the practice reads a document, the compliance checks of the back office.
-
Private messaging for base-bundle: member-to-member conversations with an inbox, archives, read state, quotas and flood control
-
Marketplace for base-bundle: stores, products and variants, carts and orders, payment through pluggable gateways, sales rules (discounts, fees, taxes), reviews
-
A musician's site on omnibase: discography with the label in front, repertoire, videos, instrument, performers, and a dependency-free player - the listening links through omnisense/omnisong.
-
A newsletter for omnibase: subscribers with double opt-in, campaigns written in the back office and sent through Messenger, a monthly digest drafted from the site’s sources.
-
The notarial regime on omnibase/office: a notary's office site within its professional rules - the regulated tariff and the discounts displayed, the consumer mediator of the notariat, e-mail addresses ending in notaires.fr, the declaration to the chamber, wording checked against comparison, no online payment; fields of practice, the client's space on the encrypted vault, and who of the office reads a document.
-
A professional practice on omnibase - the office, its team, its hours and contact (core), appointments by slot or by request (Booking), an encrypted document vault per recipient with its access log (Share), a video room with a waiting room, its calls carried by a omnisense/omnimeet gateway - from browser to browser by default (Visio). Shared by the regulated professions: health, notaries, lawyers.
-
Press for omnibase: quotes, hi-res photos with credits, biographies in three lengths - the press kit page an artist’s agency asks for.
-
A restaurant on omnibase: the dining room and its layouts (a floor-plan editor, a QR poster per table), meal services and table reservations (availability under a lock, a public form, a management link, ICS), the menu (dishes as omnibase/marketplace products, sections, set menus, EU allergens), ordering at the table by QR code (sessions, rounds, tickets), the pass for the staff, and the delivery and booking platforms through omnisense/omnifood.
-
Scholar for omnibase: a researcher's site - publications read from OpenAlex, HAL, Crossref and the other omnisense/omnischolar sources, validated before they show, with manual overrides that survive each sync; the CV (positions, degrees, awards, grants, courses, supervisions), research themes and projects; publication, book, CV and teaching pages, BibTeX / RIS exports, schema.org JSON-LD.
-
Social publishing for omnibase: a reel rendered from the site’s own template (ffmpeg), published on each network through omnisense/omnipost, and the account’s feed cached for a wall on the site.
-
A video platform on omnibase: videos and channels, resumable uploads through tusd, HLS transcoding with ffmpeg, a player that keeps playing across pages, views, likes, timed comments, playlists, subscriptions, reports, a members' studio, local suggestions (Gorse optional) and a Typesense index.
-
Omniauth's Google sign-in, under any PHP host, over league/oauth2-google: Google as an OpenID Connect provider for omniauth's identity providers (Omniauth\OAuth\) - scopes "openid email profile", the nonce in the authorization address, the ID token's issuer, audience, authorized party, lifetime, nonce and Workspace domain ("hd") checked, "email_verified" read as Google sends it, the userinfo when there is no ID token -, its factory for a host's configuration.
-
Abandoned: omniauth's sign-in through identity providers is omnisense/omniauth's own since 2026-10-23 (Omniauth\OAuth\, the same namespace and class names; each provider a package of its own, omniauth/google first). This last release holds no code and requires omnisense/omniauth: require omnisense/omniauth instead.
-
Omniauth's one-time passwords over spomky-labs/otphp, under any PHP host - authenticator applications (TOTP; HOTP possible): the second factor, its enrolment (a secret and its otpauth:// address) and its revocation, with scheb/2fa's parameters (SHA1, 30 s, 6 digits, the same leeway and provisioning address) so the secrets an application keeps today go on working, a code accepted once only, and the secrets sealed at rest with libsodium (SodiumSecretBox, the key in the host's vault; the ones kept in clear read until rewritten). Formerly omniauth/totp, which it replaces (the Omniauth\Totp\ names stay aliases for one release).
-
Omniauth's WebAuthn over web-auth/webauthn-lib, under any PHP host - passkeys: the sign-in (request options, then the assertion checked: origin, relying party, user verification required, counter and backup flags kept) and the registration (creation options, then the attestation checked), on the credential record as omnibase's userPasskey table holds it - the 13 fields of WebAuthn's CredentialRecord, in their base64 text - so a passkey registered by web-auth/webauthn-symfony-bundle signs in here and one registered here is read by the bundle. A software authenticator (P-256) signs real assertions in tests. Formerly omniauth/passkey, which it replaces (the Omniauth\Passkey\ names stay aliases for one release).
-
Omnibank Bridge: bank aggregation through Bridge API v3 (bridgeapi.io) - its Connect sessions for the consent, accounts, balances, transactions, item webhooks.
-
Omnibank Files: bank statements read from the files banks export - CAMT.053, OFX (SGML and XML), CSV with a column map - and SEPA credit transfers written as pain.001.001.03. No network.
-
Omnibank Powens: bank aggregation through Powens (ex Budget Insight) - its Webview for the consent, accounts, balances, transactions, CONNECTION_SYNCED webhooks.
-
Omnibank Qonto: a Qonto organization's accounts, balances and transactions over its Business API, with an API key.
-
Omnibill AFNOR: an approved platform (plateforme agréée) through the standard API of XP Z12-013 - the Flow Service (submit an invoice, a lifecycle status or an e-reporting file, follow its acknowledgement, receive suppliers' invoices and statuses, webhooks with their signature checked) and the Directory Service (where a SIREN or a SIRET receives); any platform that implements the standard, by its address.
-
Omnibill Chorus Pro: invoices to the French public sector through PISTE - a conformant file deposited (deposer/flux), its deposit followed and the invoice's status read (rechercher/fournisseur), the PISTE client credentials and the technical account's cpro-account header.
-
Omnibill E-mail: the invoice attached to an e-mail sent through symfony/mailer, its statuses (sent, paid, refused...) kept by hand in a store of the application's - the default gateway of omnisense/omnibill, and the tests'; no platform, no approval.
-
Omnibus Amazon Shipping: rates, shipments and labels, tracking and cancellations - the Selling Partner Shipping API v2.
-
Omnibus Aramex: rates, shipments and labels, tracking and offices - the Shipping, Tracking and Location services (JSON).
-
Omnibus Australia Post: prices, shipments and labels, tracking - the Shipping and Tracking API.
-
Omnibus Blue Dart: waybills and labels, tracking - the Blue Dart API gateway.
-
Omnibus Canada Post: rates, non-contract shipments and labels, tracking and post offices - the REST (XML) web services.
-
Omnibus Canpar: rates, shipments and labels, tracking - the CanShip web services (SOAP).
-
Omnibus Chronopost: prices (Quickcost), shipments and labels, tracking and Pickup relay points - the SOAP web services.
-
Omnibus Colissimo (La Poste): rates from configuration; labels, tracking and relay points to come.
-
Omnibus DB Schenker: tracking through the eSchenker API; rates from configuration, shipments booked in the portal.
-
Omnibus DHL Express: rates, labels and tracking - MyDHL API; service points through the DHL location finder.
-
Omnibus DTDC: consignments and labels, cancellations, tracking - the DTDC customer integration API.
-
Omnibus FedEx: rate quotes, labels, tracking and locations - the REST APIs with OAuth2.
-
Omnibus GLS: shipments and labels through ShipIT, cancellations, tracking.
-
Omnibus JD Logistics: waybills, interception and traces - the JD Open Platform (signed requests).
-
Omnibus Mondial Relay carrier: relay points, labels, tracking (Web_Services.asmx, no ext-soap needed).
-
Omnibus offline carrier: the shop ships by itself - configured rates, a tracking number typed by hand, its own counters as pickup points.
-
Omnibus Purolator: estimates, shipments and labels, tracking - the E-Ship Web Services (SOAP).
-
Omnibus Royal Mail: orders and postage labels through Click & Drop, tracking through the Tracking API.
-
Omnibus SF Express: orders, cancellations and route tracking - the SF Express open API (signed requests).
-
Omnibus TNT Express: prices, shipments and labels, tracking - ExpressConnect (XML).
-
Omnibus UPS: rates, labels, tracking and Access Point locations - the REST APIs with OAuth2.
-
Omnibus USPS: prices, labels, tracking and drop-off locations - the USPS APIs v3 with OAuth2.
-
Omnibus ZTO Express: orders, cancellations and traces - the ZTO open API (signed requests).
-
Omnidns's Cloudflare, under any PHP host: the records of a zone (over cloudflare/sdk, proxying kept), and the domains Cloudflare Registrar holds for an account with their terms - an API token.
-
Omnidns's Gandi, under any PHP host: whether a domain is free and its price, registering and renewing it, the account's domains and their terms, their name servers, and LiveDNS records - Gandi's API v5 with a personal access token, on the application's HTTP client.
-
Omnidns's OVHcloud, under any PHP host: whether a domain is free and its price, registering it (a cart checked out) and renewing it, the account's domains and their terms, their name servers, and the records of their zones - over the official ovh/ovh client.
-
Omnidns's Scaleway, under any PHP host: whether a domain is free, registering and renewing it, the project's domains and their terms, their name servers, and the records of their zones - Scaleway's Domains and DNS API with a secret key, on the application's HTTP client.
-
Omnidocs Doxygen: a C or C++ project's reference from Doxygen's XML output - its main page, a page per namespace, class, struct and file with its public members, their declarations, parameters and returns; notes, warnings and code examples in omnidocs' conventions.
-
Omnidocs JSDoc: a JavaScript library's API reference from the JSON JSDoc explains (jsdoc -X) - a page per global, its functions, methods and properties with their comments, parameters and source lines; a library of browser scripts (IIFE, UMD) named by the globals it sets.
-
Omnidocs Markdown: a folder of Markdown files as an omnidocs manual - its contents from the folders and the files (their front matter, a number before their name), each page rendered with league/commonmark as symfony.com/doc writes its pages: callouts (note, tip, caution, versionadded...), code with a caption and in tabs, version badges, links between pages and to the repository; and a changelog read as releases.
-
Omnidocs PHP: a PHP package's API reference, read from its sources - its namespaces, classes, interfaces, traits and enums, their public constants, properties and methods with their signatures and PHPDoc, and the options its factories' configuration takes - as an omnidocs manual (nikic/php-parser, phpdocumentor/reflection-docblock); nothing is loaded nor run.
-
Omnidocs Sphinx: a Sphinx manual as an omnidocs manual, from the JSON builder's output (sphinx-build -b json) and its objects.inv - pages in the toctrees' order, admonitions and versionadded as callouts, highlighted code in frames, the API entries at their anchors with their signatures.
-
Omnidrive Azure: a container of Azure Blob Storage as an omnidrive drive, through azure-oss/storage-blob-flysystem (the adapter The PHP League names in place of its own, abandoned) - a connection string, a prefix, public and signed (SAS) addresses.
-
Omnidrive Dropbox: a folder of Dropbox as an omnidrive drive, through spatie/flysystem-dropbox - an access token or a refresh token renewed on its own, a prefix, temporary links.
-
Omnidrive FTP: a directory of an FTP or FTPS server as an omnidrive drive, through league/flysystem-ftp (ext-ftp) - passive mode, a server behind NAT, binary transfers, Unix modes.
-
Omnidrive Google Drive: a folder of Google Drive (My Drive or a shared drive) as an omnidrive drive, through masbug/flysystem-google-drive-ext - OAuth refresh token or service account, paths by name.
-
Omnidrive Local: a directory of this machine as an omnidrive drive, through league/flysystem-local - its root, its Unix modes, its public address, the file's local path.
-
Omnidrive S3: an S3 bucket - AWS, MinIO, Scaleway, OVHcloud, Cloudflare R2... - as an omnidrive drive, through league/flysystem-async-aws-s3: its region or endpoint, its keys, a prefix, public and signed temporary addresses.
-
Omnidrive SFTP: a directory of an SFTP server, over SSH, as an omnidrive drive, through league/flysystem-sftp-v3 (phpseclib 3, pure PHP) - a password, a private key or the SSH agent, the server's key checked, Unix modes.
-
Omnidrive WebDAV: a collection of a WebDAV server - Nextcloud, ownCloud, Apache mod_dav, any - as an omnidrive drive, through league/flysystem-webdav (sabre/dav) - basic or digest authentication, a prefix.
-
Omnifood Deliveroo: the orders (read, listed, accepted, rejected, prep stages), the menu and the items out of stock, the site opened or closed and its hours, the order and rider webhooks checked - through the Deliveroo Partner Platform APIs.
-
Omnifood Just Eat: the orders JET Connect sends to the restaurant, the menu and the items out of stock, the restaurant set offline and its service times - Just Eat, Takeaway, Skip The Dishes, Menulog - through the public JET Connect API.
-
Omnifood TheFork: the restaurant's reservations read, created, updated and cancelled, its tables closed or opened online, the webhooks read - through TheFork's B2B API (TheFork Manager).
-
Omnifood Uber Eats: the orders (read, accepted, denied, ready, cancelled), the menu and its items suspended, the store paused and its holiday hours, the webhooks checked - through the Uber Eats Marketplace APIs.
-
Omnifood Zenchef: the restaurant's credentials and a client ready for Zenchef's partner API, whose documentation Zenchef sends on request - every reservation call refused until it is public.
-
Omnifund's GitHub Sponsors, under any PHP host: a user's or an organization's listing read through GitHub's GraphQL API - its page, its goal, its tiers, the number of sponsors and the public ones.
-
Omnifund's Liberapay, under any PHP host: an account's public profile read from Liberapay's public.json - patrons counted, weekly income, goal, summary (no key; Liberapay keeps patrons and tiers private).
-
Omnifund's Open Collective, under any PHP host: a collective read through Open Collective's GraphQL API v2 - its profile and yearly budget, its tiers, its backers (public data, no key needed; a personal token raises the rate limit).
-
Omnilab Bright Sky: the Deutscher Wetterdienst's open data through Bright Sky - hourly weather at a point or a DWD or WMO station, the observations back to 2010 joined to the MOSMIX forecasts (temperature, dew point, humidity, precipitation and its probability, pressure, wind and gusts, cloud cover, visibility, sunshine, solar irradiation), or days made from the hours; a station as an entity; no key needed.
-
Omnilab Cactus: the NCI/CADD Chemical Identifier Resolver - a structure from a name, a CAS number, an InChIKey, an InChI or a SMILES, and its standard InChIKey, InChI, SMILES, IUPAC name, formula, molecular weight, CAS numbers, names and picture; OPSIN for a name it cannot read; no key.
-
Omnilab CAMS: the Copernicus Atmosphere Monitoring Service's Atmosphere Data Store - its datasets (European air quality forecasts and reanalyses, global atmospheric composition, greenhouse gases, fire emissions, solar radiation) as products over a place and a period, its catalogue's search, a dataset's variables and request form, what a request would cost, read without an account; with an account's key, a request submitted and followed until its file is the product's asset. The store runs the Climate Data Store's software: omnilab/cds's source, on the ADS.
-
Omnilab CDS: the Copernicus Climate Data Store - its datasets (ERA5, ERA5-Land, seasonal forecasts, climate projections, satellite and in-situ observations) as products over a place and a period, its catalogue's search, a dataset's variables and request form, what a request would cost, read without an account; with an account's key, a request submitted and followed until its file (NetCDF, GRIB, zip) is the product's asset to download. The client of ECMWF's data stores, which omnilab/cams uses for the Atmosphere Data Store.
-
Omnilab ChEBI: a chemical entity of biological interest by ChEBI id, InChIKey, CAS number, KEGG id or name - its definition, formula, masses, charge, SMILES, InChI, structure depiction, its ontology (what it is a kind of, its roles, functional parents, conjugates) and its identifiers in CAS, KEGG and the other bases - and a search, through the REST API of ChEBI 2.0 (EMBL-EBI), no key needed.
-
Omnilab ChEMBL: a bioactive molecule by ChEMBL id, InChIKey or name - its type, maximum development phase, computed properties (molecular weight, ALogP, polar surface area, hydrogen bond donors and acceptors, Lipinski's rule of five, QED), SMILES, InChI, structure depiction, mechanisms of action and their targets, and its identifiers in ChEBI, PubChem, UNII and DSSTox through UniChem - and a search by text or InChIKey, through the ChEMBL data web services (EMBL-EBI), no key needed.
-
Omnilab ClinVar: a variation by its VariationID or VCV accession - its name, type, germline classification, review status, conditions, genes, protein change, consequence, location, SPDI, allele frequencies, aliases - its dbSNP id as a cross-reference, its genes and conditions (Mondo, OMIM, Orphanet, HPO) as related things, and a search in ClinVar's query language, through the NCBI's E-utilities, no key needed.
-
Omnilab COD: a crystal structure of the Crystallography Open Database by its COD id (9008565) - its names, formula, unit cell with uncertainties, space group, Z, temperature, radiation, R factors, publication and DOI - the entry it duplicates as a related thing, its CIF as a file; a search of the entries' metadata; no key.
-
Omnilab CODATA: the fundamental physical constants of CODATA as NIST publishes them (2022 adjustment) - each constant by NIST's short name (mp, c) or its name, its value, standard uncertainty and unit, whether exact, its value as published; a search; two calls in all, no key.
-
Omnilab Catalogue of Life: a taxon or synonym of the Catalogue of Life by its COL id, by the GBIF key that names it (GBIF's taxonomy is the COL eXtended Release) or by its name - authority, rank, status, classification, vernacular names, distribution, scrutinizer, source record; its GBIF key and the iNaturalist, WoRMS or ITIS records COL names as cross-references; parent, accepted name and synonyms related - and a search of names, through ChecklistBank's API, no key needed.
-
Omnilab Copernicus: the products of the Copernicus Data Space Ecosystem's STAC catalogue - Sentinel-1, -2, -3, -5P, Landsat, MODIS, the Copernicus DEM and services - searched by collection, point or box, period and cloud cover, page by page, with their footprints, properties, assets and thumbnails; open without an account (downloading the assets needs a CDSE token and stays with the application).
-
Omnilab DONKI: NASA's space weather events from the CCMC's Database Of Notifications, Knowledge, Information - solar flares (GOES class, begin, peak, end, source, active region), coronal mass ejections (speed, half angle, direction, type), geomagnetic storms (Kp), interplanetary shocks, solar energetic particle events, magnetopause crossings, radiation belt enhancements, high speed streams - by activity id, or every event of a period, with the events each is linked to; no key needed.
-
Omnilab Earthdata: NASA's Common Metadata Repository (CMR) - the granules of NASA's Earth observation collections (HLS, MODIS, VIIRS, GPM, SMAP, ICESat-2, OPERA...) as products by collection, point or box, period and cloud cover, page by page, with their footprints, attributes, browse images and files (https at the archive, s3 in AWS); the collections searched by text; open without an account, the files downloaded with an Earthdata Login token (an option).
-
Omnilab eBird: a bird taxon of the eBird/Clements taxonomy by its species code (no key) - scientific and common names in a locale, category, order, family, banding codes - and, with the user's eBird API key, a taxon by name, a search of names, a checklist, and the recent observations around a point or in a region or a region's observations of a day, through the eBird API 2.0.
-
Omnilab Elevation: the elevation of points and of a profile between two points from a digital elevation model (SRTM, ASTER, EU-DEM, Mapzen, ETOPO1, GEBCO...), through Open Topo Data's public API or a self-hosted instance, as Points with their elevation in metres, outside the contract's shapes; no key needed (100 locations a call, a call a second, 1,000 a day on the public instance).
-
Omnilab EMSC: an earthquake of the European-Mediterranean Seismological Centre's catalogue by its SeismicPortal id - magnitude and type, place, depth, time, Flinn-Engdahl region, contributing agency - and the earthquakes of a box or around a point over a period as series (count per step, each one's magnitude or depth, or the step's maximum, mean...) or as occurrences, entities with their time and place a page at a time, through the SeismicPortal's FDSN event web service, no key needed.
-
Omnilab Ensembl: a gene, transcript, protein or exon of Ensembl by its id, or a gene by its symbol in a species - its symbol, name, biotype, species, assembly and place on the genome, a gene's NCBI Gene record and Swiss-Prot proteins and a protein's UniProt entries as cross-references, its species, gene, transcripts and protein as related things - and the genes a symbol names, through the Ensembl REST API, no key needed.
-
Omnilab NASA Exoplanet Archive: a confirmed exoplanet by its name (51 Peg b, Kepler-22b, Proxima Centauri b, Dimidium) - its mass, radius, density, orbit, equilibrium temperature and insolation with units and uncertainties, how, when and where it was discovered, its host star's parameters and the system's position, distance and magnitudes, the host star's designations (HD, HIP, TIC, Gaia DR3) as a related thing - a search by name and a selection by simple criteria, through the archive's TAP service in ADQL, no key needed.
-
Omnilab Gaia: a source of ESA's Gaia DR3 by its source_id or designation (Gaia DR3 4472832130942575872) - its position at epoch J2016.0, parallax, proper motion and RUWE, its G, BP, RP and RVS magnitudes, radial velocity and line broadening, its astrophysical parameters (GSP-Phot temperature, gravity, metallicity, distance, extinction; FLAME radius, mass, luminosity, age; Apsis spectral type), its class probabilities and Hipparcos number - and the sources of a cone on the sky, through the ESA Gaia Archive's TAP service in ADQL, no key needed.
-
Omnilab GBIF: a taxon of GBIF's taxonomy (the Catalogue of Life eXtended Release since June 2026) by its key, its legacy GBIF Backbone number, its NCBI Taxonomy id or a scientific name GBIF matches - its name, authority, rank, status, IUCN Red List category, common name, publication and classification, its legacy number and NCBI id as cross-references, its parent as a related thing - a search, and the occurrences of a place and a period (by taxon, country, basis of record), each with its time and place and its taxon related, through the GBIF API, no key needed.
-
Omnilab GWAS Catalog: a study by its accession (GCST000854), a variant by its rs id, a trait by its EFO, Mondo or HPO id - reported and mapped traits, samples, ancestries, platforms, functional class, location, mapped genes, studies - each with its strongest associations and the studies, variants and traits they tie it to as related things, a search of traits, and the associations paged with their p-values, effect sizes and risk alleles, through the NHGRI-EBI GWAS Catalog's REST API v2, no key needed.
-
Omnilab HGNC: a human gene by its HGNC id (HGNC:4827), approved, previous or alias symbol, or an id HGNC records (NCBI Gene, Ensembl, UniProt, OMIM) - its approved name, locus group and type, location, previous symbols and names, aliases, gene groups, status, dates, MANE Select, RefSeq and CCDS ids - its NCBI Gene, Ensembl, UniProt and OMIM ids as cross-references, and a search, through HGNC's REST service, no key needed.
-
Omnilab Horizons: the ephemeris of a body of the solar system - a planet, a moon, the Sun, an asteroid, a comet, a spacecraft - seen from a place on the Earth over a period, as series: right ascension and declination, azimuth and elevation, airmass, apparent magnitude, illuminated fraction, angular diameter, distances to the observer and to the Sun and their rates, solar elongation and phase angle, through NASA/JPL's Horizons API, no key needed.
-
Omnilab iNaturalist: a taxon of iNaturalist by its id or a name it matches - its rank, common name in a language, iconic group, IUCN status, lineage, Wikipedia summary, observation count, default photo with its licence and attribution, its parent as a related thing - a search of its names, and the observations of a place and a period (research grade by default; by taxon, licence, quality grade), each with its time and place, its taxon related and its licence, through the iNaturalist API (v1 for taxa, v2 for observations), no key needed.
-
Omnilab InterPro: an InterPro entry (IPR000971) or a Pfam family (PF00042) - its name, type, description, member signatures, GO terms, protein and structure counts, Pfam clan, representative structure, overlapping entries and hierarchy - a UniProt protein with the InterPro entries and Pfam families it matches, by type and position, as related things, and a search of InterPro entries, through the InterPro API, no key needed.
-
Omnilab ITIS: a taxon of the Integrated Taxonomic Information System by its TSN or its name - authority, rank, usage and why, accepted name, hierarchy, common names, geographic divisions, jurisdictional origins, credibility rating; parent, accepted name, synonyms and children related - and a search of scientific and common names, through the ITIS JSON web service, no key needed.
-
Omnilab IUCN Red List: a taxon of the IUCN Red List of Threatened Species by its SIS id or scientific name - classification, authority, common names, synonyms, assessing group - with its latest global assessment (Red List category, criteria, population trend, year, possibly extinct, citation), through the Red List API v4 with the user's API token.
-
Omnilab JPL: an asteroid or a comet by its number, designation or name, from NASA/JPL's Small-Body Database API - its orbit (elements at their epoch with their uncertainties, period, MOID), physical parameters (absolute magnitude, diameter, albedo, rotation period, density, spectral types), NEO and PHA flags, discovery and IAU citation, close approaches to the Earth and Sentry's impact risk - and a search by name or designation (SBDB Query API), no key needed.
-
Omnilab KEGG: a compound (C07481), a drug (D00528), a reaction (R00200), a pathway map (map00010, hsa00010) or an enzyme (2.7.1.40) by its KEGG identifier - names, formula and masses, a reaction's equation, a pathway's class and description, an enzyme's class and systematic name - the same thing in CAS, ChEBI, ChEMBL and Rhea as identifiers, its reactions, pathways, enzymes, compounds and GO terms as related things; a compound by its ChEBI id; a search; through KEGG's REST API (rest.kegg.jp), for academic use by academic users only.
-
Omnilab Launches: orbital launches of The Space Devs' Launch Library 2, past and planned - a launch by id (rocket, provider, mission and orbit, pad and its place, date and its precision, window, status, probability, failure), a search by text, and the launches of a period as occurrences, each with its time and its pad's place, filtered by provider, rocket, location, crew, status or orbit; no key needed (15 calls an hour).
-
Omnilab Materials Project: computed properties of inorganic materials by Materials Project id (mp-149) - formula, symmetry, density, energies per atom, stability, band gap, magnetism, elastic moduli - and the materials of a formula or a chemical system, through api.materialsproject.org (an account's key required). Not tested live.
-
Omnilab MPC: a minor planet, comet or natural satellite of the IAU's Minor Planet Center by its number, designation (provisional, packed or not) or name - its designations, name and naming citation, its orbit as the MPC computes it (osculating elements with their uncertainties, perihelion, period, MOIDs), absolute magnitude, observations, oppositions, arc and uncertainty parameter; a search of the names; its latest observations - through the MPC's APIs, no key needed.
-
Omnilab NCBI: a gene of NCBI Gene by its GeneID - symbol, name, organism, place on the genome, summary, its UniProt and Ensembl ids - and a taxon of NCBI Taxonomy by its id or a name - scientific name, rank, lineage, common name, GBIF key - and a search of either, through NCBI Datasets v2 and E-utilities, no key needed (one for ten calls a second).
-
Omnilab NED: an object of the NASA/IPAC Extragalactic Database - a galaxy, a quasar, a cluster, a radio source - by any of its names: its preferred name, type, J2000 position with its uncertainty, redshift with its uncertainty and quality, galactic coordinates, and how many references, photometric points, redshift-independent distances, images and spectra NED holds for it; the objects of a cone on the sky - through NED's ObjectLookup and TAP services, no key needed.
-
Omnilab NOAA: weather and climate observations as series at a point - the station records of the world from NCEI's Access Data Service (GHCN-Daily by day, the Global Summary of the Month and of the Year: TMAX, TMIN, TAVG, PRCP, SNOW, AWND... in metric units) at the nearest station that has them or at a station named, and, for a point of the United States, the National Weather Service's observations of the nearest station (seven days back) joined to its grid's forecast (seven days ahead); no key.
-
Omnilab OBIS: a marine taxon of the Ocean Biodiversity Information System by its WoRMS AphiaID or its name - rank, status, classification, vernacular names, NCBI id, habitat, how many records OBIS holds - and the occurrences of a place and a period (by taxon, depth, dataset, Red List species), each with its time, place, depth, the sea surface temperature and salinity at its place, its taxon related, through the OBIS API v3, no key needed.
-
Omnilab Open-Meteo: weather series at a point - hourly, every 15 minutes or daily, any variable Open-Meteo names, with the units it answers in - from the forecast API (92 days back, 16 ahead) and the historical archive (ERA5, from 1940), joined when a period spans both; and the air quality at a point (PM2.5, PM10, NO2, O3, the European and US indices, pollens...), hourly or daily, from 2013 to five days ahead; free for non-commercial use, a key or a self-hosted instance otherwise.
-
Omnilab OpenAQ: air quality measurements of the OpenAQ platform (API v3) - the hourly or daily averages of a pollutant (PM2.5, PM10, NO2, O3, SO2, CO, black carbon... by OpenAQ's parameter names) at the nearest location of a point measuring it, in the sensor's unit. An OpenAQ API key is required (the user's own, sent as X-API-Key); not tested live.
-
Omnilab Open Targets: a target by its Ensembl gene, a disease or phenotype by its EFO, Mondo, HPO or Orphanet id, a drug by its ChEMBL id - names, descriptions, locations, classes, therapeutic areas, parents, mechanisms of action, indications - their associations with scores, drugs and clinical candidates, UniProt, HGNC, OMIM and Orphanet ids, InterPro domains and Reactome pathways, a search, and the associations paged, through the Open Targets Platform's GraphQL API, no key needed.
-
Omnilab OQMD: the Open Quantum Materials Database - an entry by its OQMD id (formula, space group, prototype, volume, formation energy, hull distance, band gap, ICSD id) and the entries of a composition or a phase space, through its RESTful API, no key. Not tested live.
-
Omnilab PBDB: a taxon of the Paleobiology Database, fossil or living, by its number or name - rank, accepted name, common name, extant or not, first and last appearances (intervals and ages in Ma), occurrences counted, classification, ecology, reference - a fossil occurrence by its number, a search of names, and the fossil occurrences of a place and an age (outside the contract: an age is no date), through the PBDB data service 1.2, no key needed.
-
Omnilab PDB: an entry of the Protein Data Bank by its PDB id through RCSB PDB's GraphQL Data API - its title, keywords, method, resolution, weight, dates, primary citation and authors, its polymer entities and ligands, an image of its assembly; the UniProt proteins of its chains, their organisms and its ligands (ChEBI, PubChem or InChIKey) as related things, never its identifiers; a removed entry's only replacement - and RCSB's full-text search, no key needed.
-
Omnilab PubChem: a compound by CID, name, InChIKey, InChI, CAS number or SMILES - its computed properties with units (formula, weight, XLogP, TPSA...), synonyms, description, 2D structure image and its identifiers in ChEBI, ChEMBL, Wikidata, CAS, UNII, DSSTox and KEGG - through PubChem's PUG-REST, no key needed, at PubChem's pace.
-
Omnilab QuickGO: a Gene Ontology term (GO:0005829) - its name, definition, aspect, synonyms, comment, obsolescence, direct parents by relation and children - a UniProt protein with the GO terms it is annotated to by aspect and evidence, its annotations with their evidence, reference and curator, and a search of terms, through the EBI's QuickGO services, no key needed.
-
Omnilab Reactome: a pathway or a reaction by its stable identifier (R-HSA-70171) - its names, species, summary, compartments, GO biological process, Rhea reaction, inputs, outputs and catalysts, review status, release dates, DOI and diagram - its participants (UniProt proteins, ChEBI small molecules), organism, sub-events and orthologous events as related things, a search by text, and the pathways of a protein or a molecule (UniProt, ChEBI), through Reactome's Content Service, no key needed.
-
Omnilab Rhea: a biochemical reaction by any of its four Rhea ids (18157, 18160) or its KEGG reaction (R00200) - its equation, status, balance, transport, sides and their participants, citations - its quartet and KEGG reaction as identifiers, its ChEBI participants, EC numbers, GO term, Reactome events and the reviewed UniProt proteins that catalyse it as related things; a search; through Rhea's SPARQL endpoint and REST search, no key.
-
Omnilab SIMBAD: an astronomical object beyond the solar system by any of its identifiers (M31, Betelgeuse, HD 39801...) - its main identifier, object type, ICRS coordinates, proper motion, parallax, radial velocity and redshift, spectral and morphological types, magnitudes and other designations - and a search by identifier or name, through the TAP service of SIMBAD (CDS, Strasbourg) in ADQL, no key needed.
-
Omnilab STRING: a protein by its STRING id (9606.ENSP00000269305), UniProt accession, Ensembl protein or name - its preferred name, protein name, annotation, species and Ensembl protein - its interaction partners as related things with their combined scores, the network among proteins with each evidence channel's score, and their functional enrichment (GO, KEGG, Reactome, Pfam, InterPro, diseases), through STRING's API, no key needed.
-
Omnilab SWPC: NOAA's Space Weather Prediction Center - the probability of an aurora overhead at a point (OVATION's nowcast) as a series, and outside the contract, space weather not being at a place on the Earth, the planetary Kp index observed and predicted, the solar wind at L1 (speed, density, temperature, Bt, Bz), the alerts, warnings and watches, and the NOAA scales; through SWPC's public JSON files, no key needed.
-
Omnilab Tides: NOAA CO-OPS (Tides and Currents) - a station's water level every six minutes, verified hourly heights and highs and lows, tide predictions (every six minutes, hourly, or the highs and lows), water and air temperature as series, at a station named or the nearest one of a point, cut to the API's length limits; a station as an entity; through the CO-OPS Data and Metadata APIs, no key needed.
-
Omnilab UniProt: a protein of UniProtKB by accession or entry name - its names, gene, organism, function, length, mass and sequence, cofactors, ligands, location and keywords, its NCBI Gene and Ensembl genes as cross-references, its organism, PDB structures and ligands as related things - and UniProt's search, through the UniProt REST API, no key needed.
-
Omnilab USGS: an earthquake of the USGS catalogue (ComCat) by its event id - magnitude and type, place, depth, time, felt reports and intensities (DYFI, ShakeMap), tsunami flag, PAGER alert level, its ids in the other networks - and the earthquakes of a box or around a point over a period as series (count per step, each one's magnitude or depth, or the step's maximum, mean...) or as occurrences, entities with their time and place a page at a time, through the FDSN event web service, no key needed.
-
Omnilab USGS Water: the USGS's water data through the Water Data OGC APIs (which replace the WaterServices) - a monitoring location's series (discharge, gage height, water temperature, any parameter by its USGS code) as recorded every 5 or 15 minutes, hourly, or as the USGS's daily statistics, at a station named or the nearest one of a point; a monitoring location as an entity with its place, drainage area and the series it keeps; the locations by name. No key needed; an api.data.gov key raises the rate limit.
-
Omnilab VizieR: the CDS's library of published astronomical catalogues (Strasbourg) - its tables whose description holds a text, as datasets (id, catalogue, title, authors, rows), and the rows of a table around a point of the sky or an object, each column with its unit and description - through TAPVizieR in ADQL, no key needed.
-
Omnilab Wikidata: an item by Q-number, by the identifier of a science base its statements carry (PubChem CID, ChEBI, CAS, InChIKey, ChEMBL, UniProt, NCBI Gene and Taxonomy, Ensembl, GBIF, iNaturalist, SIMBAD, JPL SBDB, USGS earthquake, UNII, DSSTox, KEGG) or by label - its label, description and aliases in the language asked, those identifiers as cross-references, a few properties with units (mass, melting and boiling points, density...) - and a search by label, narrowed to a domain, through the Wikidata Action API, no key needed, within Wikimedia's usage policy.
-
Omnilab WoRMS: a taxon of the World Register of Marine Species by its AphiaID, its name, or the ITIS TSN, NCBI taxon or IUCN id WoRMS knows it by - accepted name and status, classification, synonyms, vernacular names, habitat flags, the citation WoRMS asks for, its ITIS, NCBI and IUCN ids as cross-references - and a search of names, through the WoRMS REST service, no key needed.
-
Omnilex EUR-Lex: EU law and the case law of the Court of Justice from the Publications Office's open endpoint (Cellar: SPARQL and resources by CELEX number) - an act in its consolidated version at a date, one article of it, a judgment by ECLI, the links between acts and judgments, what is new - no key.
-
Omnilex Judilibre: the decisions of the Cour de cassation and of the judicial courts from the Judilibre API (PISTE) - search with filters, one decision with its zones, the texts it applies and the case law it is brought together with, what changed since a date; pseudonymised, never re-identified.
-
Omnilex justice administrative: the decisions of the Conseil d'État, the administrative courts of appeal and the administrative tribunals from their open data (opendata.justice-administrative.fr) - search by text, court, kind and dates, one decision with its full text, what was added since a date - no key.
-
Omnilex Légifrance: codes, laws, decrees and the Journal officiel from the Légifrance API (PISTE) - a text or one article as in force at a date, search in the codes, the consolidated texts and the case law, the links of an article, the texts published since a date.
-
Omnimap's Google Maps, under any PHP host: the live map drawn by the Maps JavaScript API (a driver for omnimap's script: markers, styled map types by zoom), a view as a Static Maps image (the URL signed with the secret), geocoding through geocoder-php's GoogleMaps provider, and glitchr/ux-google's names for the pictures it captured.
-
Omnimap's MapLibre, under any PHP host: the live map drawn by MapLibre GL JS from a vector style (OpenFreeMap's by default: no key, no cookie), a driver for omnimap's script, and the style read on the server to name every host the browser reaches.
-
Omnimap's OpenStreetMap, under any PHP host: the live map drawn by Leaflet over a tile server of your choice (a driver for omnimap's script), a view as an image made on the server from the same tiles (the application's User-Agent, the tiles kept as their Cache-Control allows, the attribution drawn), and Nominatim's geocoding through geocoder-php (one call a second at most, answers kept).
-
Omnimeet Direct: a video meeting from browser to browser (WebRTC) - two people, encrypted end to end, no third party, nothing recorded. The handshake's rules on a store the application provides, temporary TURN credentials for one's own relay (coturn's use-auth-secret), and the JavaScript engine, with no dependency.
-
Omnimeet Jitsi: a video meeting on a Jitsi Meet instance - one's own, a public one, or 8x8's Jitsi as a Service - embedded through the IFrame API and driven from the page, a JSON Web Token per participant (shared secret or key pair), several people, JaaS webhooks read and their signature checked.
-
Omniplay's Docker hosting, under any PHP host: game-server containers started and stopped through the Docker Engine API (a unix socket or TCP), the image, command and environment of each service given by configuration, the server's ticket secret handed to it in its environment.
-
Omniplay's Edgegap hosting, under any PHP host: game servers deployed through Edgegap's REST API near the players given (their public IPs or coordinates) or near a region's location, the deployment's status read until it has an address, stopped by its request id; the server's ticket secret handed to it in its environment, hidden.
-
Omniplay's GOG, under any PHP host, with no key: a product's record with its description and its price in the country asked, and the catalogue's search with prices, studios, genres and the store's rating.
-
Omniplay's IGDB, under any PHP host: Twitch's games database through Apicalypse queries - search, a game's record by its IGDB, Steam or GOG number with its studios, platforms, cover and screenshots, score and identifiers on the stores; Twitch's application token got and renewed by itself.
-
Omniplay's itch.io, under any PHP host: a game page's record from its public data.json with no key, and with a server-side API key whether a player owns one of your games (download keys) and the library of the key's own account.
-
Omniplay's RAWG, under any PHP host: search and a game's record with its studios, platforms, scores and the stores that sell it - its Steam number, itch.io page and Epic slug read from their links - with an API key.
-
Omniplay's Steam, under any PHP host: an app's store record and the store's search with no key (price in the country asked, texts in the language asked), a player's library and whether they own a game with a Steam Web API key, and a player's Steam session ticket verified on the platform (ISteamUserAuth/AuthenticateUserTicket) with the publisher key given by reference, answering the player's SteamID. Lobbies stay in the game, through the Steamworks SDK.
-
Omnipost Instagram: the account's feed, the publication of pictures, carousels and reels, and the long-lived token's refresh, through the Instagram API with Instagram Login.
-
Omnipost YouTube: the channel's videos through the Data API (a key), and Shorts uploaded through OAuth.
-
Omnireach's Bing Webmaster Tools, under any PHP host: a site's search queries and pages in Bing with their clicks, impressions, CTR and average position, week by week or over a period, through the Bing Webmaster API (JSON, API key).
-
Omnireach's Google Analytics 4, under any PHP host: visitors, sessions, pageviews, bounce rate and session length of a property, by landing page, page, source, country, device or day, through the Google Analytics Data API (runReport; a service account's key or an access token).
-
Omnireach's Matomo, under any PHP host: visits, visitors, pageviews, bounce rate and visit length of a site, by entry page, page, referrer, country, device or day, through Matomo's Reporting API (self-hosted or Matomo Cloud), the token sent by POST.
-
Omnireach's Plausible, under any PHP host: visitors, visits, pageviews, bounce rate and visit duration of a site, by page, entry page, source, country, device or day, through Plausible's Stats API v2 (plausible.io or a self-hosted Community Edition).
-
Omnireach's Google Search Console, under any PHP host: a property's search queries, pages, countries and devices with their clicks, impressions, CTR and average position, day by day or over a period, through the Search Console API (a service account's key or an access token).
-
Omnireview Google: an establishment's Google rating and reviews through the Places API (New) - up to five, with their authors' attribution - and, for its owner, every review and replying through the Business Profile API; the link to leave a review; Google's display and caching rules declared.
-
Omnireview Tripadvisor: a location's rating, bubbles and up to five reviews through Tripadvisor's Content API, the link to write one; its display requirements declared - logo, bubbles from Tripadvisor's addresses, pages kept out of search engines.
-
Omnireview Trustpilot: a business unit's TrustScore and reviews, the links to its profile and to review it, replying and inviting customers with the business user's token; Trustpilot's 24-hour refresh declared.
-
Omnischolar arXiv: preprints by author name, arXiv id or search, with abstracts, categories, PDFs and the DOI of the published version - no key, three seconds between calls.
-
Omnischolar Crossref: the reference metadata of any Crossref DOI, the works deposited with an ORCID, a bibliographic search - no key, in the polite pool with a mailto.
-
Omnischolar HAL: the deposits of the French open archive by idHAL, ORCID or name, their open-access full texts, and a filter by domain (shs.droit for legal scholarship) - no key.
-
Omnischolar INSPIRE-HEP: high-energy physics authors (BAI, ORCID), their positions and citation summary, their literature with citation counts - no key.
-
Omnischolar OpenAlex: an author's profile and counts (works, citations, h-index), their works with abstracts, citations and open-access links, any work by DOI - through the OpenAlex API, no key needed.
-
Omnischolar Open Library: an author's books, one record per edition with ISBNs, publisher and cover, for the Merger to group - no key.
-
Omnischolar ORCID: a researcher's identity, CV (employments, education, distinctions...) and declared works, through ORCID's public API - no key.
-
Omnisearch Typesense: omnisearch's driver for Typesense, over glitchr/typesense-bundle - the indexes declared by omnisearch's attributes become the bundle's collections (sub-collections of a discriminator included), objects its documents, omnisearch's requests its queries (infix, matched tokens, facets...), its responses omnisearch's; in a Symfony application the bundle hosts them.
-
Omnishield Akismet: is this content spam - comment-check (ham, spam, or flagrant spam to discard), submit-spam and submit-ham to teach it, verify-key; a key or transport error raised, never taken for ham.
-
Omnishield ALTCHA: a proof of work the site issues and checks itself, on altcha-org/altcha - a challenge signed with the site's key, the solution the visitor's browser found checked, a solution refused the second time; no third party, no cookie.
-
Omnishield Disposable: is this e-mail's domain a disposable one - the free disposable-email-domains list (CC0) shipped in the package, an allow list and a deny list of the site's, subdomains included; no call while a request runs, a command to refresh the list.
-
Omnishield reCAPTCHA: Google's captcha - v2 checkbox and invisible, v3 score with its threshold and action, and reCAPTCHA Enterprise assessments - its token checked by direct calls, no Google library.
-
Omnishield StopForumSpam: are this IP address, this e-mail (sent hashed), this name reported for abuse - the public database's frequency, confidence and last sighting, a threshold of the site's; reports with an API key.
-
Omnishield Turnstile: Cloudflare's captcha - the widget, and its token checked by Cloudflare's siteverify (the visitor's address, the action and the host checked back, a request retried under its idempotency key).
-
Omnishow's YouTube, under any PHP host: a video's record (title, description, duration, thumbnails, date, channel, its player and the privacy-enhanced youtube-nocookie one), a search, a channel by its identifier or @handle and its uploads, playlists, what a channel broadcasts live and has scheduled - through the YouTube Data API v3 with an API key.
-
Omnisign DocuSeal: documents signed on a DocuSeal instance of one's own (open source, AGPL) or DocuSeal's cloud - a submission from a template, or from a PDF where the edition allows it, its submitters, embedded signing, reminders, the signed documents and the audit log, webhooks with their X-Docuseal-Signature checked; nothing leaves for a third party when self-hosted.
-
Omnisign DocuSign: envelopes through DocuSign's eSignature REST API v2.1 - JWT grant with the application's RSA key, documents, signers in order, signature tabs, embedded signing (recipient views), reminders, voiding, the combined signed document and the certificate of completion, Connect webhooks with their HMAC checked.
-
Omnisign Yousign: simple, advanced and qualified electronic signatures through Yousign's public API v3 (Youtrust since its new name) - a signature request built from documents, signers and fields, activated, followed, reminded, cancelled; signing in the application's page; the signed documents and the audit trail; webhooks with their signature checked.
-
Omnisong iTunes: an artist's albums and tracks with their 30-second previews and artwork, through the iTunes Search API - no key.
-
Omnisong Odesli: one link to the same song or album on every platform, through song.link's API.
-
Omnistate Annuaire des Entreprises: French companies from the State's Recherche d'entreprises API (INSEE Sirene + INPI's RNE) - free, no key.
-
Omnistate Annuaire Santé: French health professionals (RPPS: profession, specialties, workplaces, MSSanté addresses) and facilities (FINESS) from the ANS's FHIR API.
-
Omnistate IANA: domains, IP addresses and AS numbers through IANA's RDAP bootstrap - the registrar, the dates, the name servers, who holds a network. Free, no key.
-
Omnistate matchID: France's deaths since 1970 (INSEE's file of deceased persons) searched through deces.matchid.io - names, birth, death, the act's number.
-
Omnistate NARA: the National Archives Catalog of the United States (Catalog API v2) - federal files that name a person (pension files, military service records, draft cards, naturalization indexes), with their reference and links to their scanned pages. A catalogue, not civil registration; an API key is needed.
-
Omnistate National Archives UK: the Discovery catalogue of the UK's National Archives and 2,500 other archives - documents that name a person (wills, service records, parish papers), with their reference. A catalogue, not civil registration.
-
Omnistate Open Archives: births, baptisms, marriages, deaths, burials and more from the indexes of Dutch and Belgian archives (openarchieven.nl), with the archive's reference and the scan of the act.
-
Omnistate VIES: EU VAT numbers checked with the European Commission's VIES (REST - no SOAP extension needed), with a consultation number as proof.
-
Omniticket's Billetweb, under any PHP host: an organizer's events with their rates, sessions and places left, the attendees of an event (incrementally, as Billetweb asks), and a ticket's barcode checked at the door - read only, through Billetweb's API v1.
-
Omniticket's Eventbrite, under any PHP host: an organization's events with their ticket classes, price range and availability, the attendees of an event (incrementally), and a ticket's barcode checked among them - read only, through Eventbrite's API v3.
-
Omniticket's HelloAsso, under any PHP host: an association's event forms with their tiers, the registrations of an event, and a ticket's QR code checked among them - read only, through HelloAsso's API v5 (OAuth2 client credentials).
-
Omniticket's Ticketmaster, under any PHP host: public events from the Discovery API (dates, venue, price range, sale status, the purchase link) - a catalogue, read only.
-
Omniticket's Weezevent, under any PHP host: an organizer's events with their rates (categories flattened), sessions and sales period, the participants of an event (incrementally), and a ticket's barcode checked at the door - read only, through Weezevent's API (api.weezevent.com).
-
Omnitrade Amazon: products read through Amazon's Creators API (the successor of the Product Advertising API 5) and affiliate links with the Associates tag.
-
Omnitrade PayPal: orders approved on PayPal's page and captured on return, authorizations, refunds and webhook events, over the v2 REST API.
-
Omnitrade Shopify: a sale paid on the shop's invoice page (draft orders), the shop's orders, its catalogue (products, variants, inventory) and its webhooks, over the Admin GraphQL API.
-
Omnitrade Stripe: cards and wallets through Checkout (the hosted page), refunds, webhook events and the catalogue of Stripe Products and Prices, on omnipay/stripe.
-
Omnitrade Web: any product page read from its own markup - JSON-LD Product (and ProductGroup), microdata, OpenGraph - as an Omnitrade Product, and affiliate links by host.
-
Omnitrade WooCommerce: a sale paid on the shop's checkout (orders created unpaid), the shop's orders and their payment state, refunds, the catalogue (products, variations, stock) and webhooks, over the REST API v3.
-
Navigation without page loads (and a website in the website), sticky scroll effects, scroll stops, scroll-driven scenes, sortable lists, AJAX channels, cookies and consent - one library, one module per feature
-
A layered directed graph you can drag and zoom: HTML nodes, SVG links, no dependency