GreyNoise Intelligence · Arazzo Workflow

GreyNoise IP Context Timeline

Version 1.0.0

Pull an IP's full context, then chart its activity timeline if observed.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub SecurityThreat IntelligenceCybersecurityIP ReputationVulnerability ManagementNetwork TelemetrySOC AutomationPublic APIsArazzoWorkflows

Provider

greynoise

Workflows

ip-context-timeline
Context an IP, then chart its activity timeline when it has been seen.
Fetches the full IP context and, when the IP has been observed by the sensor network, retrieves its noise activity timeline summary for a given field.
2 steps inputs: apiKey, days, field, granularity, ip outputs: classification, firstSeen, seen, timeline
1
fullContext
Retrieve the full IP context and determine whether the IP has been observed by the GreyNoise sensor network.
2
timeline
Retrieve the IP's summary of noise activity for the chosen field over the requested window of days at the requested granularity.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: GreyNoise IP Context Timeline
  summary: Pull an IP's full context, then chart its activity timeline if observed.
  description: >-
    Builds a temporal picture of a single IP. The workflow first retrieves the
    full IP context and branches on whether GreyNoise has actually observed the
    IP; when it has been seen, it pulls the noise activity timeline for a chosen
    field (such as classification or destination_port) over a window of days.
    Every step spells out its request inline so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: ipLookupApi
  url: ../openapi/greynoise-ip-lookup-api-openapi.yml
  type: openapi
- name: ipTimelineApi
  url: ../openapi/greynoise-ip-timeline-api-openapi.yml
  type: openapi
workflows:
- workflowId: ip-context-timeline
  summary: Context an IP, then chart its activity timeline when it has been seen.
  description: >-
    Fetches the full IP context and, when the IP has been observed by the sensor
    network, retrieves its noise activity timeline summary for a given field.
  inputs:
    type: object
    required:
    - apiKey
    - ip
    properties:
      apiKey:
        type: string
        description: GreyNoise API key passed via the 'key' HTTP header.
      ip:
        type: string
        description: The IPv4 address to investigate (e.g. 36.32.2.102).
      field:
        type: string
        description: The field to break activity down by in the timeline.
        default: classification
      days:
        type: string
        description: Number of days of timeline data to show.
        default: '7'
      granularity:
        type: string
        description: Granularity of activity date ranges (e.g. 8h or 1d).
        default: 1d
  steps:
  - stepId: fullContext
    description: >-
      Retrieve the full IP context and determine whether the IP has been
      observed by the GreyNoise sensor network.
    operationId: V3IP
    parameters:
    - name: key
      in: header
      value: $inputs.apiKey
    - name: ip
      in: path
      value: $inputs.ip
    - name: quick
      in: query
      value: false
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      seen: $response.body#/internet_scanner_intelligence/seen
      classification: $response.body#/internet_scanner_intelligence/classification
    onSuccess:
    - name: observed
      type: goto
      stepId: timeline
      criteria:
      - context: $response.body
        condition: $.internet_scanner_intelligence.seen == true
        type: jsonpath
    - name: neverSeen
      type: end
      criteria:
      - context: $response.body
        condition: $.internet_scanner_intelligence.seen == false
        type: jsonpath
  - stepId: timeline
    description: >-
      Retrieve the IP's summary of noise activity for the chosen field over the
      requested window of days at the requested granularity.
    operationId: getIPTimelineFieldSummary
    parameters:
    - name: key
      in: header
      value: $inputs.apiKey
    - name: ip
      in: path
      value: $inputs.ip
    - name: field
      in: query
      value: $inputs.field
    - name: days
      in: query
      value: $inputs.days
    - name: granularity
      in: query
      value: $inputs.granularity
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      results: $response.body#/results
      firstSeen: $response.body#/metadata/first_seen
  outputs:
    seen: $steps.fullContext.outputs.seen
    classification: $steps.fullContext.outputs.classification
    timeline: $steps.timeline.outputs.results
    firstSeen: $steps.timeline.outputs.firstSeen

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/greynoise-ip-context-timeline-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.