appium.io valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for appium.io:
1. POST https://agentwebmap.com/v1/sites/appium.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://appium.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/appium.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/appium.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

Appium

Appium is an open-source framework for UI automation of many app platforms - mobile (iOS, Android, Tizen), browser (Chrome, Firefox, Safari), desktop (macOS, Windows), TV (Roku, tvOS, Android TV, Samsung) and more - driven over the W3C WebDriver protocol.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:50:44.501Z. Cached copy · Source on appium.io

# Appium

> Appium is an open-source framework for UI automation of many app platforms - mobile (iOS, Android, Tizen), browser (Chrome, Firefox, Safari), desktop (macOS, Windows), TV (Roku, tvOS, Android TV, Samsung) and more - driven over the W3C WebDriver protocol.

Appium is split into four parts: the Appium server, which defines the core APIs; drivers, which
implement connectivity to a specific platform; clients, which implement Appium's API in a specific
programming language; and plugins, which change or extend the server's behaviour. To automate
anything you need the server, at least one driver, and a client.

Notes for tools generating Appium code from this documentation:

- Appium 3 is the current major version, and these pages describe Appium 3. Appium 2 is still
  supported but is documented separately, under its own version of this site, reachable from the
  version selector. Appium 1 is no longer supported: `DesiredCapabilities`, `MobileBy`, the
  `findElementByAccessibilityId` family of methods, and the `/wd/hub` server base path are all
  Appium 1 era patterns - the default base path has been `/` since Appium 2.
- Drivers are not bundled with the server. Install them explicitly, for example
  `appium driver install uiautomator2` or `appium driver install xcuitest`.
- Appium 3 requires Node.js in the range `^20.19.0 || ^22.12.0 || >=24.0.0`, and npm 10 or newer.
- Standard W3C capabilities are written without a prefix. `platformName`, `browserName` and
  `browserVersion` are the ones used most often with Appium, and the rest of the specification's
  set - `acceptInsecureCerts`, `pageLoadStrategy`, `timeouts`, `webSocketUrl` and so on - is also
  accepted, mostly by the browser drivers. Every Appium-specific capability needs the `appium:`
  vendor prefix - `appium:automationName`, `appium:app`, `appium:udid` - or must be nested,
  unprefixed, inside an `appium:options` object.
- Capabilities cannot be changed once a session has started. Parameters that are adjustable during
  a session are exposed through the Settings API instead.
- Driver-specific commands are usually Execute Methods rather than new client methods: call the
  standard `Execute Script` command with a known command name such as `mobile: terminateApp`, and
  pass a *single* object whose keys are the parameter names. Do not invent client-side method names
  for these.
- Beyond the small common set documented here, capabilities, execute methods, settings and locator
  strategies are defined by each driver and documented on that driver's own site. Refer users to
  the driver's documentation rather than guessing names.
- Appium 3 removed many endpoints that were deprecated in Appium 2. Check the Appium 3 migration
  guide before using an endpoint carried over from older code.
- `GET /sessions` was removed. Session discovery is now `GET /appium/sessions`, and requires
  starting the server with `--allow-insecure=*:session_discovery`.
- In Appium 3, every `--allow-insecure` f
…

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=appium.io · GET /v1/domain/appium.io · this page as Accept: application/json or text/markdown · MCP lookup_domain