API Evangelist enrichment overlay for the Syft Data Lookup API

# generated: '2026-08-13'
# method: generated
# source: overlays openapi/syft-data-lookup-api-openapi.yml with API Evangelist enrichment metadata
overlay: 1.0.0
info:
  title: API Evangelist enrichment overlay for the Syft Data Lookup API
  version: 1.0.0
extends: ../openapi/syft-data-lookup-api-openapi.yml
actions:
  - target: $.info
    update:
      x-apisio-enriched: true
      x-apisio-provider: syft-data
      x-apisio-auth: Server Secret Key (sk_live_) via Authorization Bearer, x-syft-secret-key header, or secretKey body field
      x-apisio-lifecycle: alpha — access-gated to select customers; interface may change
      x-apisio-rate-limits: none published; see rate-limits/syft-data-rate-limits.yml
      x-apisio-plans: Credit-metered; see plans/syft-data-plans-pricing.yml
  - target: $.paths['/syft/lookup'].post
    update:
      x-apisio-notes: >-
        Observation-only. Returns companies and contacts Syft has already seen on
        your site or LinkedIn ads; it will not enrich arbitrary emails or domains
        and returns 404 when the entity is unknown.
      x-apisio-result-caps:
        contacts_per_company: 10
        sessions_per_contact: 10
      x-apisio-mcp-equivalent: lookup_entities
      x-apisio-idempotency: >-
        None. A read expressed as POST with no idempotency key; safe to retry but
        the provider makes no guarantee.
  - target: $.components.schemas.Company
    update:
      x-apisio-intent-scale: [low, medium, high, very_high]
  - target: $.components.schemas.Error
    update:
      x-apisio-error-format: >-
        Flat { "error": "..." } envelope, not RFC 9457 problem+json. See
        errors/syft-data-problem-types.yml.