EOEPCA User Client

How tools, CLIs, and libraries discover and talk to an EOEPCA+ deployment.

Clients start from a single entry point, /.well-known/api-catalog, and follow typed links to workspace, catalogue, processing, identity, and other services.

What’s in this repo

Path	Purpose
docs/	Building-block docs: design, API Catalog spec, getting started
eoepca-client/	Python library and eoepca CLI

Full documentation: Read the Docs

Quick start

Fetch the catalog for a deployment (when it serves /.well-known/api-catalog):

curl -sS https://<deployment>/.well-known/api-catalog | jq .

The develop deployment does not serve that endpoint yet; inspect the reference document instead:

jq . docs/api/schema/example.json

Use the Python client (requires uv and Python 3.12+):

cd eoepca-client
uv tool install .          # not on PyPI yet — install from this repo
eoepca login -p develop    # built-in develop endpoints; prompts for credentials
eoepca whoami

See eoepca-client/README.md for library usage, STAC commands, and development setup.