GEODNET RTK

Service overview

What is GEODNET RTK?

GEODNET provides RTK positioning access through a partner-approved account flow. In peaqOS, the operator supplies GEODNET appId and appKey request-scoped as `providerCredentials.geodnet`, then a paired Machine Agent can search, order, execute `query-rtk-account`, and receive order, run, outcome, and audit records. Provider billing stays with the GEODNET partner account; peaqOS records the orchestration lifecycle and redacts credentials before persistence.

How it works

1. Step 1

   Get partner access

   Request GEODNET Enterprise RTK API access and receive the issued appId and appKey.

2. Step 2

   Send scoped credentials

   Pass appId and appKey under providerCredentials.geodnet when searching or executing through peaqOS.

3. Step 3

   Query the RTK account

   Call query-rtk-account with input.username; peaqOS routes the request and stores the run, outcome, and audit trail.

Adapter operations

Behind peaqOS — operator calls peaqOS, peaqOS calls GEODNET with request-scoped partner credentials.

• GETquery-rtk-account

  Look up the status of a GEODNET RTK account by username; returns the account payload.

Integration fields

Wire GEODNET RTK into peaqOS

serviceId

geodnet:rtk-account:partner

skillKey

geodnet-rtk-account

serviceType

data.location

operation

query-rtk-account

credential path

providerCredentials.geodnet.appId/appKey

input field

input.username

Provider access

Set up GEODNET RTK on the provider

FAQ

Questions agents ask about GEODNET RTK

• Does it require manual setup?+

  Yes. Follow the provider’s setup docs to create an account and obtain the required API credentials. Send them as request-scoped provider credentials when your agent calls peaqOS, and peaqOS routes calls to the provider on your behalf.

• How does payment work?+

  No peaqOS marketplace payment runs for this service. Usage is billed by the provider on your account at whatever rate they set. peaqOS still records the order, execution, and audit receipt so robots have provable history.

• How deterministic are responses?+

  Depends on the upstream service. Text-generation endpoints expose temperature; deterministic services return the same payload on the same input.

• What happens if a request fails?+

  The provider returns its own error response — auth, rate-limit, quota, etc. peaqOS surfaces it to the agent, which can retry, refresh credentials, or fall back to another service.