craterview 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- craterview-0.1.0/LICENSE +202 -0
- craterview-0.1.0/PKG-INFO +288 -0
- craterview-0.1.0/README.md +260 -0
- craterview-0.1.0/craterview/__init__.py +622 -0
- craterview-0.1.0/craterview.egg-info/PKG-INFO +288 -0
- craterview-0.1.0/craterview.egg-info/SOURCES.txt +9 -0
- craterview-0.1.0/craterview.egg-info/dependency_links.txt +1 -0
- craterview-0.1.0/craterview.egg-info/requires.txt +1 -0
- craterview-0.1.0/craterview.egg-info/top_level.txt +1 -0
- craterview-0.1.0/pyproject.toml +45 -0
- craterview-0.1.0/setup.cfg +4 -0
craterview-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 CraterView
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,288 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: craterview
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Python client for the CraterView image enhancement API
|
|
5
|
+
Author-email: Bernardt Duvenhage <bernardt.duvenhage@gmail.com>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://craterview.ai
|
|
8
|
+
Project-URL: Documentation, https://api.craterview.ai/docs
|
|
9
|
+
Project-URL: Source, https://github.com/craterviewai/craterview-python
|
|
10
|
+
Project-URL: Issues, https://github.com/craterviewai/craterview-python/issues
|
|
11
|
+
Keywords: upscaling,super-resolution,image-restoration,api-client
|
|
12
|
+
Classifier: Development Status :: 3 - Alpha
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: Operating System :: OS Independent
|
|
15
|
+
Classifier: Programming Language :: Python :: 3
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.9
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
20
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
21
|
+
Classifier: Topic :: Multimedia :: Graphics :: Graphics Conversion
|
|
22
|
+
Classifier: Topic :: Scientific/Engineering :: Image Processing
|
|
23
|
+
Requires-Python: >=3.9
|
|
24
|
+
Description-Content-Type: text/markdown
|
|
25
|
+
License-File: LICENSE
|
|
26
|
+
Requires-Dist: requests>=2.31
|
|
27
|
+
Dynamic: license-file
|
|
28
|
+
|
|
29
|
+
# craterview
|
|
30
|
+
|
|
31
|
+
Python client for the [CraterView](https://craterview.ai) image enhancement and
|
|
32
|
+
restoration API.
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
pip install craterview
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
Python 3.9 or newer. `requests` is the only dependency.
|
|
39
|
+
|
|
40
|
+
## Quickstart
|
|
41
|
+
|
|
42
|
+
```python
|
|
43
|
+
from craterview import CraterView
|
|
44
|
+
|
|
45
|
+
cv = CraterView(api_key="cv_...")
|
|
46
|
+
result = cv.run("photo.jpg", style="photo")
|
|
47
|
+
result.save("photo-4x.jpg")
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
`run()` collapses the upload → submit → poll sequence into one call. That sequence is the
|
|
51
|
+
API's shape rather than an accident, but it is not something every caller should have to
|
|
52
|
+
reimplement.
|
|
53
|
+
|
|
54
|
+
## An API key
|
|
55
|
+
|
|
56
|
+
Keys begin with `cv_` and are issued from your dashboard. Pass one to the constructor, or
|
|
57
|
+
leave it out and the client talks to the API unauthenticated — useful only against a local
|
|
58
|
+
development gateway.
|
|
59
|
+
|
|
60
|
+
```python
|
|
61
|
+
cv = CraterView(api_key=os.environ["CRATERVIEW_API_KEY"])
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
A key carries your whole allowance and does not expire, so keep it server-side. It is a
|
|
65
|
+
credential for programs; it is not a login.
|
|
66
|
+
|
|
67
|
+
## The one call
|
|
68
|
+
|
|
69
|
+
```python
|
|
70
|
+
job = cv.run(
|
|
71
|
+
image, # path, str, bytes, or a file object
|
|
72
|
+
model="cv-restore-v1", # default
|
|
73
|
+
wait=30.0, # seconds to hold the connection open
|
|
74
|
+
timeout=600, # total seconds before giving up
|
|
75
|
+
raise_on_failure=True,
|
|
76
|
+
**params, # model parameters, e.g. style="photo"
|
|
77
|
+
)
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
It waits server-side first, so a job that finishes quickly costs a single round trip, then
|
|
81
|
+
falls back to polling for anything slower. With `raise_on_failure=False` a failed job is
|
|
82
|
+
returned rather than raised, and `job.error` says why.
|
|
83
|
+
|
|
84
|
+
Which parameters a model accepts is published by the API rather than hard-coded here — see
|
|
85
|
+
`cv.models()`.
|
|
86
|
+
|
|
87
|
+
## The explicit path
|
|
88
|
+
|
|
89
|
+
Useful when you want to hold the key, submit later, or fan out.
|
|
90
|
+
|
|
91
|
+
```python
|
|
92
|
+
input_key = cv.upload("photo.jpg") # → "inputs/..."
|
|
93
|
+
job = cv.submit("cv-restore-v1", input_key, style="photo")
|
|
94
|
+
job = cv.wait_for(job, timeout=600)
|
|
95
|
+
data = job.bytes()
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Image bytes never pass through the API. `upload()` PUTs them straight to object storage on
|
|
99
|
+
a presigned URL and `bytes()` GETs the result the same way; the API moves keys, not pixels.
|
|
100
|
+
|
|
101
|
+
## Retries are yours to write
|
|
102
|
+
|
|
103
|
+
**This client does not retry.** That is deliberate: only the caller knows where one logical
|
|
104
|
+
request ends and the next begins, and a retry the client invented would be a second job you
|
|
105
|
+
are billed for.
|
|
106
|
+
|
|
107
|
+
What it gives you instead is a key generator. Make one key per *logical request* and reuse
|
|
108
|
+
it for every attempt at that request:
|
|
109
|
+
|
|
110
|
+
```python
|
|
111
|
+
from craterview import new_idempotency_key
|
|
112
|
+
|
|
113
|
+
key = new_idempotency_key() # once, before the first attempt
|
|
114
|
+
for attempt in range(3):
|
|
115
|
+
try:
|
|
116
|
+
job = cv.submit("cv-restore-v1", input_key, idempotency_key=key, style="photo")
|
|
117
|
+
break
|
|
118
|
+
except (ConnectionError, TimeoutError):
|
|
119
|
+
continue # same key, so at most one job is ever created
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
Generating a fresh key per attempt defeats the point entirely — the server has nothing to
|
|
123
|
+
match against and every attempt starts its own job. Reusing a key with a *different* body
|
|
124
|
+
is rejected with 409 rather than quietly handing back the earlier result. Claims are kept
|
|
125
|
+
for 24 hours; past that the same key starts new work.
|
|
126
|
+
|
|
127
|
+
## Errors
|
|
128
|
+
|
|
129
|
+
Everything raised by this client descends from `CraterViewError`, so one `except` catches
|
|
130
|
+
the lot. `.status` carries the HTTP status where there was one.
|
|
131
|
+
|
|
132
|
+
| Exception | Meaning |
|
|
133
|
+
|---|---|
|
|
134
|
+
| `RateLimited` | 429. `.retry_after` is seconds until the window rolls over. |
|
|
135
|
+
| `JobFailed` | The job ran and did not succeed. `.args[0]` says what you can do about it; `.error_code` is the half to branch on. |
|
|
136
|
+
| `CraterViewError` | Everything else, including 4xx and 5xx from the API. |
|
|
137
|
+
|
|
138
|
+
## `Job`
|
|
139
|
+
|
|
140
|
+
Every field the API publishes on a job is exposed here.
|
|
141
|
+
|
|
142
|
+
| | |
|
|
143
|
+
|---|---|
|
|
144
|
+
| `id`, `model`, `status` | `status` is one of `queued`, `running`, `succeeded`, `failed` |
|
|
145
|
+
| `created_at` | Timezone-aware `datetime` |
|
|
146
|
+
| `succeeded`, `done` | `done` covers both terminal states |
|
|
147
|
+
| `error` | Set when the job failed. Safe to show a user |
|
|
148
|
+
| `error_code` | The same fact, as a stable identifier. Branch on this, show the other |
|
|
149
|
+
| `credits` | **What you were billed** |
|
|
150
|
+
| `eta_seconds` | The estimate made at submit. Absent once the job has settled |
|
|
151
|
+
| `community` | True when the job is on the community queue: served after priority work, taking a small share of it |
|
|
152
|
+
| `output_url`, `download_url` | The result, presigned. One to display, one to save |
|
|
153
|
+
| `thumb_url` | A small JPEG of the result, for listings. Null when none was drawn |
|
|
154
|
+
| `input_url` | The file you sent. Null once it has expired — inputs go after a day |
|
|
155
|
+
| `output_content_type` | The result's media type |
|
|
156
|
+
| `output_bytes` | The result's size in bytes |
|
|
157
|
+
| `bytes()`, `save(path)` | Download the result |
|
|
158
|
+
|
|
159
|
+
`result` is the whole of what the job produced, and the five rows above it that describe the
|
|
160
|
+
file are accessors onto `result["output"]` rather than separate fields — the API states those
|
|
161
|
+
links once. A model with no file to hand back returns its answer in `result` and leaves every
|
|
162
|
+
one of them null.
|
|
163
|
+
|
|
164
|
+
`credits` is the only figure about cost the API states, and the price is fixed and published
|
|
165
|
+
per model, so an invoice reconciles against `credits` alone. For how long a job took, subtract
|
|
166
|
+
`created_at` from `finished_at` — that is the wait you had, queue included.
|
|
167
|
+
|
|
168
|
+
**Uploads declare their size.** `upload()` and `run()` measure the bytes they are about
|
|
169
|
+
to send and declare that figure; the API signs it into the presigned URL, so storage accepts
|
|
170
|
+
exactly that length and nothing else. You do not pass it — it is read off the data in hand,
|
|
171
|
+
which is what makes it impossible to get wrong.
|
|
172
|
+
|
|
173
|
+
**Running out of credit does not stop you.** A job submitted against a balance of zero is
|
|
174
|
+
accepted, charged and run — it simply waits in the community queue for capacity that paid
|
|
175
|
+
work is not using, and comes back with `community` set. There is no payment error to
|
|
176
|
+
handle: credit buys a place at the front of the queue rather than the right to submit.
|
|
177
|
+
`eta_seconds` covers the whole wait, queue time included, so a community job simply
|
|
178
|
+
reports a longer one.
|
|
179
|
+
|
|
180
|
+
`output_url` and `download_url` are the same object signed two ways; the content
|
|
181
|
+
disposition is signed in, so the second cannot be derived from the first. Both expire, so
|
|
182
|
+
fetch the result rather than storing the link.
|
|
183
|
+
|
|
184
|
+
`thumb_url` and `input_url` are for building a job listing: a few-hundred-pixel preview so a
|
|
185
|
+
page of results costs kilobytes, and the original so a result can be shown against what made
|
|
186
|
+
it. They keep very different company on expiry — the preview lives as long as the result,
|
|
187
|
+
while inputs are deleted a day in — so treat a missing `input_url` as normal rather than as
|
|
188
|
+
an error.
|
|
189
|
+
|
|
190
|
+
## Webhooks
|
|
191
|
+
|
|
192
|
+
Pass `webhook_url` on submit — an absolute `http` or `https` URL, refused at submit if it is
|
|
193
|
+
not one — and we `POST` to it once the job settles. Verify every delivery before you act on
|
|
194
|
+
it: anyone who learns your URL can send you a plausible-looking body.
|
|
195
|
+
|
|
196
|
+
```python
|
|
197
|
+
from craterview import CraterView, verify_webhook, InvalidSignature
|
|
198
|
+
|
|
199
|
+
secret = CraterView(api_key="cv_...").webhook_secret() # created the first time you ask
|
|
200
|
+
|
|
201
|
+
@app.post("/hooks/craterview")
|
|
202
|
+
def hook(request):
|
|
203
|
+
try:
|
|
204
|
+
event = verify_webhook(request.body, request.headers, secret)
|
|
205
|
+
except InvalidSignature:
|
|
206
|
+
return 400 # not from us; do nothing at all
|
|
207
|
+
|
|
208
|
+
# Answer now and work afterwards. A slow endpoint is retried while it is still
|
|
209
|
+
# working, so treat deliveries as at-least-once and make this idempotent on `id`.
|
|
210
|
+
enqueue(event["id"])
|
|
211
|
+
return 200
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
Every copy of a delivery states the same thing, so the first one you accept is the whole
|
|
215
|
+
answer — later copies of an `id` you have already handled can be dropped rather than
|
|
216
|
+
reconciled.
|
|
217
|
+
|
|
218
|
+
**Pass the raw bytes.** Most frameworks parse JSON for you, and re-serialising it changes the
|
|
219
|
+
bytes the signature was computed over. In Flask that is `request.get_data()`, in Django
|
|
220
|
+
`request.body`, in FastAPI `await request.body()`.
|
|
221
|
+
|
|
222
|
+
The body carries the same fields a job read does, by the same names — including `result` and
|
|
223
|
+
the links inside it. The one difference is what happens to a field that does not apply: a
|
|
224
|
+
callback states every key and sets it `null`, where a job read leaves it out. So a subscriber
|
|
225
|
+
parses one shape and never has to ask which keys arrived.
|
|
226
|
+
|
|
227
|
+
The links expire like any others. A delivery normally arrives within seconds of the job
|
|
228
|
+
settling and they are good for an hour, but a subscriber that queues work for later should
|
|
229
|
+
read the job again rather than storing them.
|
|
230
|
+
|
|
231
|
+
### Rotating the secret
|
|
232
|
+
|
|
233
|
+
```python
|
|
234
|
+
new = cv.rotate_webhook_secret()
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
The old secret keeps being sent alongside the new one for a day, and `verify_webhook` accepts
|
|
238
|
+
either — so deploy the new one whenever suits rather than the moment you asked for it.
|
|
239
|
+
|
|
240
|
+
## Managing keys
|
|
241
|
+
|
|
242
|
+
```python
|
|
243
|
+
cv.keys() # every key on the account, by prefix; revoked ones stay listed
|
|
244
|
+
cv.create_key("staging") # the value is in this response and nowhere else
|
|
245
|
+
cv.revoke_key("key_...") # immediate, and not reversible
|
|
246
|
+
```
|
|
247
|
+
|
|
248
|
+
Several keys on one account is the ordinary arrangement — one per service or environment, so
|
|
249
|
+
revoking one leaves the others working. They share the account's credits and history.
|
|
250
|
+
|
|
251
|
+
To rotate without downtime: create the new key, move your clients onto it, then revoke the
|
|
252
|
+
old one. You cannot revoke the key you are calling with.
|
|
253
|
+
|
|
254
|
+
## Everything else
|
|
255
|
+
|
|
256
|
+
```python
|
|
257
|
+
cv.models() # models, their parameter schemas, and queue depth
|
|
258
|
+
cv.jobs(limit=50, status="succeeded") # your history, newest first, paging transparently
|
|
259
|
+
cv.job("job_...") # one job by id
|
|
260
|
+
cv.usage() # credit balance, spend and job counts
|
|
261
|
+
```
|
|
262
|
+
|
|
263
|
+
`jobs()` is a generator and pages for you.
|
|
264
|
+
|
|
265
|
+
## Configuration
|
|
266
|
+
|
|
267
|
+
```python
|
|
268
|
+
CraterView(
|
|
269
|
+
api_key=None,
|
|
270
|
+
base_url="https://api.craterview.ai",
|
|
271
|
+
timeout=60.0, # per-request, seconds
|
|
272
|
+
)
|
|
273
|
+
```
|
|
274
|
+
|
|
275
|
+
`base_url` is what you change to point at a local gateway.
|
|
276
|
+
|
|
277
|
+
## Versioning
|
|
278
|
+
|
|
279
|
+
Semver, from `0.1.0` on. A release that removes a public name, renames an attribute on `Job`
|
|
280
|
+
or changes the type of one, gets a minor bump while this is `0.x` and a major bump after
|
|
281
|
+
`1.0.0`; anything purely additive gets a patch. Pin what you depend on.
|
|
282
|
+
|
|
283
|
+
The API this wraps adds fields to its responses without warning, so treat an unfamiliar key in
|
|
284
|
+
`result` or a `status` you do not recognise as something to ignore rather than to fail on.
|
|
285
|
+
|
|
286
|
+
## License
|
|
287
|
+
|
|
288
|
+
Apache-2.0. See [LICENSE](LICENSE).
|