generated: '2026-08-04'
method: derived
source: openapi/fieldpulse-api-openapi-original.json + https://help.fieldpulse.com/api-reference/getting-started
description: Cross-cutting and industry standards the FieldPulse Open API does and
  does not conform to, derived from the published OpenAPI and documentation. Absence
  is recorded as data, not as a defect.
standards:
- id: openapi-3.0
  conforms: true
  evidence: openapi/fieldpulse-api-openapi-original.json declares openapi 3.0.0 with
    57 paths and 109 operations; served publicly at https://help.fieldpulse.com/openapi/fieldpulse-api.json
- id: rest
  conforms: true
  evidence: Resource-oriented paths with GET/POST/PUT/DELETE mapped to retrieve/create/update/delete,
    documented in Getting Started.
- id: json
  conforms: true
  evidence: All responses are returned in JSON format (Getting Started, item 4).
- id: api-key-auth
  conforms: true
  evidence: components.securitySchemes.apiKeyAuth — apiKey in header, name x-api-key;
    applied globally via the root security requirement.
- id: oauth2
  conforms: false
  evidence: No oauth2 security scheme in the spec; no OAuth documentation; /.well-known/oauth-authorization-server
    returns 404 on every host.
- id: oidc
  conforms: false
  evidence: /.well-known/openid-configuration returns 404 on every host.
- id: rfc9457-problem-details
  conforms: false
  evidence: 'Error responses use application/json with a bare message-string body;
    no application/problem+json anywhere in the spec.'
- id: rfc9116-security-txt
  conforms: false
  evidence: /.well-known/security.txt returns 404 on help.fieldpulse.com and www.fieldpulse.com.
- id: rfc8594-sunset-header
  conforms: false
  evidence: No Sunset or Deprecation header support documented; no deprecated operations
    in the spec.
- id: rfc9110-rate-limit-headers
  conforms: partial
  evidence: A RateLimit-Reset header is returned on 429 responses only; no RateLimit-Limit
    or RateLimit-Remaining on successful responses.
- id: idempotent-writes
  conforms: false
  evidence: No idempotency key header or parameter documented or present in the spec.
- id: pagination
  conforms: true
  evidence: page/limit query parameters with documented defaults (page 1, limit 20,
    max 100) and an opt-in calculate_count total.
- id: json-api
  conforms: false
  evidence: No JSON:API media type or document structure.
- id: odata
  conforms: false
- id: scim2
  conforms: false
  evidence: Users and Teams are read-only single-collection endpoints; no /Users
    SCIM schema, no /ServiceProviderConfig.
- id: fhir
  conforms: false
  evidence: Not a healthcare API.
- id: psd2
  conforms: false
- id: mcp
  conforms: true
  evidence: A live MCP server at https://help.fieldpulse.com/mcp reports protocol version
    2025-06-18 and answers initialize, tools/list, and resources/list anonymously.
    Scope is documentation retrieval, not the product API.
  see: mcp/fieldpulse-mcp.yml
- id: a2a
  conforms: true
  grade: conformant
  evidence: An A2A 1.0.0 Agent Card is served at https://help.fieldpulse.com/.well-known/agent-card.json
    (protocolVersion 0.3, capabilities object, skills array). One deviation — interfaces
    declared under supportedInterfaces rather than additionalInterfaces.
  see: a2a/fieldpulse-a2a.yml
- id: llms-txt
  conforms: true
  evidence: https://help.fieldpulse.com/llms.txt returns 200 with a complete documentation
    index (100,359 bytes).
- id: asyncapi
  conforms: false
  evidence: A webhook surface is documented in prose for Jobs, Estimates, and Invoices,
    but no AsyncAPI document is published.
  see: asyncapi/fieldpulse-events-webhooks.yml
compliance_program:
  published: false
  certifications: []
  trust_center: null
  note: No trust center, no SOC 2 / ISO 27001 / PCI DSS / HIPAA attestation page, and
    no security or compliance page was found on any FieldPulse host as of 2026-08-04.
    Probes of trust.fieldpulse.com, security.fieldpulse.com, /trust, /security, and
    /compliance all missed. Because no compliance program is published, no `Compliance`
    pointer is emitted.
x-evidence:
  fetched: '2026-08-04'