Skip to content

Service Overview

Definition

A Service is an executable capability provider that implements one or more Agreement contracts and exposes callable interfaces to agents or applications.

Role in ASA

  • Agreement defines the callable contract.
  • Service provides the actual runtime implementation of that contract.
  • Agent discovers a service, reads its agreement dependencies, and invokes concrete actions through the service endpoint.

Core Service Information

  • identity: slug, name, provider
  • summary: short description of what the service does
  • endpoint: baseUrl
  • contract binding: agreementRequirements
  • tags: capability and scenario classification
  • coverage: geo or availability scope
  • status: enabled or disabled

Relation to Agreement

  • A service should not redefine agreement semantics.
  • A service should declare which agreement versions it implements through agreementRequirements.
  • Service-specific implementation details stay behind the service boundary; agreement-level behavior remains stable for callers.

Relation to Flow

  • Agreement defines the contract.
  • Service carries the executable interface.
  • Flow describes process-level orchestration and delivery steps built around agreements and services.

Runtime Expectation

  • A service should expose stable agreement-based paths.
  • A service should publish a clear base URL for invocation.
  • A service should be verifiable through at least one concrete asactl call command after deployment or local startup.