Events API

{
  "service_type": "platform",
  "base_url": "https://1password.com",
  "auth_method": "bearer",
  "auth_config": {
    "type": "bearer",
    "description": "Events API uses a bearer token obtained from the 1Password Business account admin console."
  },
  "endpoints": [
    {
      "path": "/events",
      "method": "GET",
      "description": "Retrieves sign-in events, item usage events, and audit events. Query parameters include limit, cursor, and event types. Endpoint base is typically https://events.1password.com."
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": "Events API is part of 1Password Business, Teams, and Enterprise plans. Free personal accounts do not have access."
  },
  "rate_limits": {
    "pagination": "Use cursor-based pagination, limit up to 1000 events per request.",
    "retry": "Suggestion to implement exponential backoff on 429 responses.",
    "documented_limit": "Unknown for tokens; consult admin console. Typically high for enterprise."
  },
  "capabilities": [
    "Retrieve sign-in events",
    "Retrieve item usage events",
    "Retrieve audit events",
    "Monitor security and compliance",
    "Integrate with SIEM and log analytics tools"
  ],
  "raw_analysis": "The 1Password Events API is a RESTful API that provides access to security-related events from 1Password Business accounts. It is used primarily for security monitoring, compliance, and integration with SIEM tools. The API supports three main event types: sign-in events, item usage events, and audit events. Authentication is via a bearer token generated in the 1Password Business admin console. The API uses cursor-based pagination to fetch large volumes of events efficiently. It is a mature API, documented at https://developer.1password.com/docs/events-api/. Integration options include setup for Splunk, Datadog, and ELK stack, via custom scripts. Pricing is included in business plans; no separate cost. Rate limits are not fully public but pagination and throttling are handled via HTTP status codes."
}

2/3 tests passed

```json
{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 3.0,
    "response_parseability": 4.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 3.0,
    "latency": 8.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "plan_tier_required": "Business/Teams/Enterprise",
    "free_personal_access": false,
    "target_audience": "enterprise_orgs"
  },
  "issues": [
    "Events API requires paid Business plan or higher — free tier completely excluded, raising onboarding barrier",
    "No llms.txt file found (404), making it harder for AI agents to discover structured API documentation",
    "No consumer-grade sign-in (no SSO/magic link mentioned); likely requires enterprise email verification and admin approval",
    "Security/compliance focus implies lengthy approval processes (legal review, contracts) — not self-serve for agents"
  ],
  "recommendations": [
    "Implement llms.txt with API endpoints, authentication flow, and event schema details",
    "Offer a sandbox/test environment with read-only token access for evaluation",
    "Add 'Sign in with' (Google/GitHub/SSO) to allow instant trial for personal verification",
    "Publish clear error codes and rate limit headers in API responses for better agent debugging",
    "Add example curl commands and step-by-step 'first event in 5 minutes' guide in docs"
  ]
}
```