4

INFO

Ask the OTA bot about an op. Use the callsign of the station running an op to get information about their op. If you have your own op on the air, you can omit the callsign and receive the info for the op you are hosting.

INFO [callsign | station]

Ask about an op: yours, or the one a callsign is running.

callsign | station
Ask about another station's op. Without it, INFO reports info about the op you are running. optional
Available to
Anyone, from RF or APRS-IS.
Rate limit
1 per 3 minutes and 3 per 15 minutes

Replies

op_info_reply
{chasing} chasing, {qsos}, {points}, {minutes} min left{stay}
op_info_reply
{station} on the air{location}, {qsos}, {minutes} min left
op_info_reply
{callsign} isn't hosting an op. Send CQ or see aprsota.org/now
op_info_reply
{station}: {description}
op_info_reply
INFO! {station} DESC {description}
op_info_reply
INFO! {record}
op_info_reply
INFO! {callsign} NIL

Hints

bare INFO from a different SSID than the live op's
Your op is run by {station}. Send INFO from it. limited to 1 per 24 hours, then silent
bare INFO with no live op
You aren't hosting an op. Send CQ for ops on the air now. limited to 1 per 24 hours, then silent

Machine form

INFO! [callsign | station]

One message, or two when the host described their op: the description first, in its own message, then the whole op record. Every message opens with INFO! and the station. A station not hosting answers INFO! with its callsign and NIL.

first, only when the op has a description
INFO! {station} DESC {description}
the op record, for an op on the air
INFO! {station} {grid} {expires_at} {qsos} {incomplete} {points} {position}
a station not hosting
INFO! {callsign} NIL
FieldOn the wireMeaning
stationstringThe station running the op, SSID included. Every host command comes from it.
gridstring, or _The six-character Maidenhead locator, or null when the position is not a place.
expires_atwhole minutes leftWhen the op goes off the air unless extended. Null once ended. Derive minutes left from this.
qsosintegerConfirmed QSOs.
incompleteintegerEntries with no QSL: chasing while on the air, incomplete once ended.
pointsintegerThe op's score: the sum of its QSOs' points.
positionlatitude then longitude, signed decimal degrees, four decimals; _ _ when unplacedWhere the confirming beacon placed the host. Established once and never moved.

{description} is free text, not a record field: What the host typed after HOST. It rides in its own message and is cut to fit one.

The grammar every machine form shares is in the handbook's API section.

W1XYZ-5OTAINFO K7ABC-6
OTAW1XYZ-5K7ABC-6 on the air from DN40fb, 5 QSOs, 22 min left

If the host described their op when they sent HOST, you get their description first and the numbers second, the same order as the op’s card on the website:

W1XYZ-5OTAINFO K7ABC-6
OTAW1XYZ-5K7ABC-6: lakeshore op, HT and a signal stick
OTAW1XYZ-5K7ABC-6 on the air from DN40fb, 5 QSOs, 22 min left

A long description is truncated if necessary to fit in one APRS message. You can view the entire description of the op on the web site.

From the station running your own op, INFO reports the pileup, your QSOs and points, and the time left. While there is room under the two-hour maximum, it also says how much time a STAY would add:

K7ABC-6OTAINFO
OTAK7ABC-63 chasing, 5 QSOs, 5 pts, 22 min left. STAY adds 30 mins

Machine form example

INFO! about a host who described their op. The description comes first in a message of its own, then the record. A host who gave no description gets only the record:

W1XYZ-5OTAINFO! K7ABC
OTAW1XYZ-5INFO! K7ABC-6 DESC lakeshore op, HT and a signal stick
OTAW1XYZ-5INFO! K7ABC-6 DN40fb 22 5 3 5 40.0542 -111.5250

Read the record as station, grid, minutes left, confirmed QSOs, chasing, points, then latitude and longitude. The API over RF page has the grammar every machine form shares.