Oscar can retrieve, validate, enrich, classify, compare, summarise and transform public sector information using a combination of Oscar data, open sources and AI.
The capabilities below are examples we have already implemented. They are not fixed products or the limit of what Oscar can do. New capabilities can be configured around a client's specific information requirement, workflow or use case.
An Oscar capability is a reusable data or AI function built around public sector information. It may retrieve information from Oscar datasets or open sources, apply validation, matching, classification, summarisation or other processing, and return a useful result that can be consumed by a person, system, application or AI agent.
What information needs to be found, checked, enriched, compared, monitored, classified, summarised or transformed?
Draw from Oscar's researched datasets, public/open sources or a combination of both depending on the requirement.
Apply matching, validation, extraction, classification, summarisation, scoring or other processing to turn source information into a usable result.
Make it available through an API, integration, bespoke route, PSN, feed, application or emerging MCP-enabled access model.
The capabilities listed below are examples Oscar has already been able to deliver. A new client requirement may produce a new capability, new inputs, new outputs or a new access route.
Capability catalogue
Use the four views below to understand the same underlying capabilities from different angles: what they do, how they can be consumed, how they can fit into systems, and the technical detail available to developers.
Implemented examples
Reusable public sector data and AI functions Oscar has already implemented. These examples show the kinds of retrieval, validation, enrichment and intelligence tasks the underlying framework can support.
| Capability | What it does | Business problem | Available through | More |
|---|---|---|---|---|
Loading capabilities... | ||||
Access & licensing
The same underlying capability may be exposed through different routes. This view separates the function itself from the access, commercial and delivery model.
| Capability | PSN | API | Connector | MCP | Bespoke | Licensing | More |
|---|---|---|---|---|---|---|---|
Loading access options... | |||||||
Integrations
Where a capability needs to sit inside a CRM, product, application, data pipeline or operational workflow, this view shows the inputs, outputs and integration characteristics already defined.
| Capability | Integration summary | Input | Output | Batch | Realtime | More |
|---|---|---|---|---|---|---|
Loading integrations... | ||||||
Developer reference
Endpoints, authentication, inputs, outputs, request formats and documentation for capabilities that have a developer-accessible implementation.
| Capability | Endpoint | Method | Auth | Version | Docs | More |
|---|---|---|---|---|---|---|
Loading developer docs... | ||||||
Built around requirements
The catalogue grows as new requirements are implemented. The starting point is the information or outcome a client needs, not whether an identical capability already exists in the table.
Tell us what information you want Oscar to retrieve or work with, what you need done to it, and what a useful result should look like. We can then determine the sources, logic, AI layer and access route.
Tell us the requirement. It may map to an existing capability or become the next one added to Oscar's catalogue.