Context Agents

A Context Agent responds to a stream of content artifacts and responds with categories and, optionally, weights. These responses are cached and made available to the Scope3 agentic platform to be used for targeting or optimization.

HTTP Protocol

Request to the agent

For just artifact IDs (for instance, if you maintain your own crawler and already have content classified), Scope3 will send a GET request to an HTTP endpoint. The artifact ID will be URL encoded and appended to the end of the endpoint. For instance, if the endpoint is http://your.site.com/url= we will send http://your.site.com/url=https%3A%2F%2Fpeople.com%2Fgene-hacman-wife-betsy-arakawa-dead-inside-investigation-final-days-exclusive-11689989.

For the full Content Schema, Scope3 will send a POST request to your endpoint with the JSON in the body.

In both cases, Scope3 can append a custom header for authentication if desired.

Synchronous response

A real-time response should list artifact categories separated by commas. These should align to a taxonomy (see below).

For use in custom algorithms, responses should separate the predicted dimension (auto_intent) and the weight (1.3) with a colon: auto_intent:1.3.

Both categories and predicted dimensions can be combined in a response.

boating,fishing,auto_intent:1.3

Asynchronous classification via API or cloud storage bucket

If your workflow requires queueing the request for processing, you can also send back one or more classifications using the Artifact Classification schema via the file upload API or by writing files to a cloud storage bucket.

Throttling and content selection

We have limited throttling and content selection controls today, though we hope to build these out over time.

Targeting taxonomy

Context Agents that express targeting data for exposure in the Scope3 platform should have a defined taxonomy in YAML format:

segments:
  outdoor:
    name: "Outdoor Activities"
    cpm: 5.75
    subsegments:
      - boating:
          name: "Boating"
          has_modifier: false
          cpm: 4.50
      - fishing:
          name: "Fishing"
          has_modifier: true
          cpm: 3.25
  intent:
    name: "Intent"
    subsegments:
      - auto_intent:
          name: "Automotive Intent"
          has_modifier: true
          cpm: 7.50

Each of the values in the taxonomy should be unique and consist only of numbers, letters, and underscores.