diff options
Diffstat (limited to '90.md')
| -rw-r--r-- | 90.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -58,7 +58,7 @@ All tags are optional. | |||
| 58 | * `<input-type>`: The way this argument should be interpreted. MUST be one of: | 58 | * `<input-type>`: The way this argument should be interpreted. MUST be one of: |
| 59 | * `url`: A URL to be fetched of the data that should be processed. | 59 | * `url`: A URL to be fetched of the data that should be processed. |
| 60 | * `event`: A Nostr event ID. | 60 | * `event`: A Nostr event ID. |
| 61 | * `job`: The output of a previous job with the specified event ID. The dermination of which output to build upon is up to the service provider to decide (e.g. waiting for a signaling from the customer, waiting for a payment, etc.) | 61 | * `job`: The output of a previous job with the specified event ID. The determination of which output to build upon is up to the service provider to decide (e.g. waiting for a signaling from the customer, waiting for a payment, etc.) |
| 62 | * `text`: `<data>` is the value of the input, no resolution is needed | 62 | * `text`: `<data>` is the value of the input, no resolution is needed |
| 63 | * `<relay>`: If `event` or `job` input-type, the relay where the event/job was published, otherwise optional or empty string | 63 | * `<relay>`: If `event` or `job` input-type, the relay where the event/job was published, otherwise optional or empty string |
| 64 | * `<marker>`: An optional field indicating how this input should be used within the context of the job | 64 | * `<marker>`: An optional field indicating how this input should be used within the context of the job |