generated: '2026-08-17'
method: generated
source: >-
  openapi/santevet-toolkit-openapi.yml, openapi/santevet-reimbursement-openapi.yml,
  acquisition.api.santevet.com/api/doc, conventions/santevet-conventions.yml,
  errors/santevet-problem-types.yml
note: >-
  Generated by API Evangelist, not published by SantéVet — no provider-authored AGENTS.md or
  skill files exist on any SantéVet host. Every operationId referenced was verified to exist
  verbatim in the specification it names. The acquisition API publishes no operationIds (HTML
  reference only), so its operations are named by method and path and labelled as such.
  All three skills are deliberately READ-ONLY: this is a regulated insurer, and the write
  surface binds contracts, files claims and redirects payments.
skills:
- file: santevet-resolve-species-and-breeds.md
  name: Resolve SantéVet species and breeds
  api: openapi/santevet-toolkit-openapi.yml
  operations:
  - getEspeceCollection
  - get_species_breedsRaceCollection
  - getRaceCollection
  - getRaceItem
  read_only: true
  summary: >-
    Turn a free-text pet description into the integer species and breed identifiers every other
    SantéVet API requires. The prerequisite for quoting.
- file: santevet-quote-a-pet-policy.md
  name: Quote a SantéVet pet insurance policy
  api: openapi/santevet-toolkit-openapi.yml
  also_uses: acquisition.api.santevet.com
  operations:
  - getSvDefContratAssuranceCollection
  - get_rates_by_speciesSvDefContratAssuranceCollection
  - getSvDefOptionAppliqueeAuDefContratCollection
  - searchSvTarifsContratCollection
  - getFractionnementCollection
  - getSvPromoCollection
  unspecified_operations:
  - 'GET /rates'
  - 'GET /quotations/{id}'
  - 'GET /quotations/{uniqueId}'
  - 'GET /quotations/{id}/rates'
  - 'POST /quotations/search'
  read_only: true
  summary: >-
    Produce a pet-insurance rate from a postal code, breed and date of birth, then read the
    product catalogue, instalment plans and promotions around it. Stops short of subscribing.
- file: santevet-read-reimbursement-claims.md
  name: Read SantéVet reimbursement claims
  api: openapi/santevet-reimbursement-openapi.yml
  operations:
  - findReimbursement
  - findAllReimbursementsByAnimal
  - findAllReimbursementsByClient
  - findSchedule
  read_only: true
  summary: >-
    Retrieve claims for an animal or a client and read the PayVet third-party-payment instalment
    schedule. Documents the eight dangling identifier fields an agent cannot resolve.
excluded_flows:
  note: >-
    No skill is authored for these. Each is a consequential write on a regulated insurance
    product with no idempotency contract published anywhere in the estate, so an agent retrying
    one can bind a duplicate policy, file a duplicate claim, redirect a payment, or irreversibly
    erase a person's record.
  flows:
  - flow: subscribe a policy
    operations: ['POST /quotations/subscribe', 'POST /quotations/{id}/subscribe', 'PATCH /quotations/{id}/to-validate']
    reason: binds a real insurance contract for a real person and animal
  - flow: create or update a prospect
    operations: ['POST /prospects', 'PATCH /prospects/{id}']
    reason: writes a named person's address, e-mail, telephone and date of birth
  - flow: anonymize a prospect
    operations: ['POST /prospects/anonymize']
    reason: irreversible GDPR erasure
  - flow: file or amend a reimbursement claim
    operations: [createReimbursement, updateReimbursement]
    reason: >-
      files a claim against a live policy; updateReimbursement carries clinic_id and
      veterinary_id, so it redirects who gets paid
  - flow: mutate reference data
    operations: [putSvGroupeRaceItem, deleteSvGroupeRaceItem, putSvTarifsContratItem, deleteSvTarifsContratItem]
    reason: alters breed groupings and contract rate rows used to price every policy
shared_rules:
  auth: partner API key in the Authorization request header; 401 on every operation without it
  auth_gap: >-
    The reimbursement API declares no securityScheme at all and neither API declares a 401
    response on any operation, so the specifications understate the auth requirement.
  idempotency: none published anywhere — the reason every skill is read-only
  rate_limits: no RateLimit-*, X-RateLimit-* or Retry-After headers; no documented quota
  tracing: no request-id or correlation header
  pagination: >-
    Hydra links in the toolkit ld+json projection only; page/results_per_page on the acquisition
    quotation search; none on the reimbursement collections
  content_negotiation: >-
    prefer application/ld+json on the toolkit API — the plain-JSON projection drops the
    pagination envelope entirely
  errors: three different error envelopes across three APIs — see errors/santevet-problem-types.yml
  conventions: conventions/santevet-conventions.yml