generated: '2026-08-13'
method: generated
source: openapi/replyrai-platform-api-swagger.json
note: >-
  Packaged Agent Skills generated by API Evangelist from the operations Replyr
  publishes in its own Swagger 2.0 document at https://app.replyr.ai/api. Every
  operationId referenced was verified against that specification; none are
  invented. Replyr publishes no skills, AGENTS.md or agent instructions of its
  own, so these are third-party operating instructions, not a Replyr publication.
api: Replyr Platform API
base_url: https://app.replyr.ai/api
authentication:
  type: apiKey
  in: header
  name: X-ACCESS-TOKEN
  scopes: none
skills:
- name: replyrai-capture-and-qualify-a-lead
  file: replyrai-capture-and-qualify-a-lead.md
  description: >-
    Find or create a contact from an inbound enquiry, tag and enrich it with
    qualification data, and send the first reply.
  operations:
  - findByCustomField
  - createNewContact
  - getAccountTags
  - getTagByName
  - createTag
  - addTagToUser
  - getAccountCustomFields
  - getCustomFieldByName
  - addFieldToUser
  - sendTextMessage
  - getUserByName
- name: replyrai-run-a-sales-pipeline
  file: replyrai-run-a-sales-pipeline.md
  description: >-
    Create and move an opportunity through a pipeline — stages, values,
    comments, transfers and close-out.
  operations:
  - getPipelines
  - getPipeline
  - getPipelineStages
  - getPipelineCustomFields
  - pipelinesGetCards
  - pipelinesAddCard
  - pipelinesGetCard
  - pipelinesUpdateCard
  - pipelinesTransferCard
  - pipelinesGetComments
  - pipelinesAddComment
  - pipelinesDeleteComment
  - pipelinesDeleteCard
- name: replyrai-send-messages-across-channels
  file: replyrai-send-messages-across-channels.md
  description: >-
    Deliver text, files, products, flows and multi-action sends across WhatsApp,
    Messenger, Instagram, SMS, Telegram, Viber, RCS and web chat — on an API with
    no idempotency and no delivery webhook.
  operations:
  - findByCustomField
  - getUserByName
  - sendTextMessage
  - sendFile
  - sendFlowToUser
  - sendContent
  - sendProduct
  - getAccountFlows
  - aiSaveMessages
  - getAccountInformation
skill_count: 3
cross_references:
  conventions: conventions/replyrai-conventions.yml
  errors: errors/replyrai-problem-types.yml
  authentication: authentication/replyrai-authentication.yml
  data_model: data-model/replyrai-data-model.yml
  rate_limits: rate-limits/replyrai-rate-limits.yml
not_covered:
- area: Appointments
  reason: >-
    The Appointment entity is defined in the schema but no operation addresses
    it — there is no list, create, reschedule or cancel endpoint — so no skill
    can be grounded in real operationIds. Appointment booking is the product's
    headline use case, which makes this the most consequential gap in the
    published contract.
- area: Ecommerce checkout and payment
  reason: >-
    Cart, order and payOrder operations exist and are documented, but payOrder
    changes payment state with no idempotency key and its 402 carries no decline
    code. A skill would have to teach an unsafe retry story; the messaging skill
    points at the surface and stops there instead.